Skip to content

fix: resolve namespaced webpack sources in VS ClientApp - #2429

Draft
navya9singh wants to merge 1 commit into
microsoft:mainfrom
navya9singh:navya9singh/fix-3059183-vue-source-navigation
Draft

navya9singh wants to merge 1 commit into
microsoft:mainfrom
navya9singh:navya9singh/fix-3059183-vue-source-navigation

Conversation

@navya9singh

Copy link
Copy Markdown
Member

Summary

  • apply Visual Studio's ASP.NET ClientApp source-map fallback to webpack 5 namespaced URLs such as webpack://vue-app/...
  • keep the existing VS Code and legacy webpack:/// behavior unchanged
  • add a regression test using a Vue CLI 5-style source URL

Without this fallback, Visual Studio resolves the authored .vue source under the nonexistent wwwroot path and opens a generated [dynamic] document instead of the physical file under ClientApp.

Validation

  • browserPathResolver.test.ts: 13 passing
  • tsc --noEmit
  • dprint check src/targets/browser/browserPathResolver.ts src/targets/browser/browserPathResolver.test.ts

Recognize webpack 5 namespace URLs when applying Visual Studio's ASP.NET ClientApp source-map fallback, and cover Vue CLI 5 source paths with a regression test.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants