Skip to content
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.

Handle sources referenced in multiple sourcemaps #315

Open
roblourens opened this issue Mar 23, 2018 · 1 comment
Open

Handle sources referenced in multiple sourcemaps #315

roblourens opened this issue Mar 23, 2018 · 1 comment
Assignees
@roblourens
Labels
bug

Comments

@roblourens
Copy link
Member

In rare cases, scripts can be referenced in multiple sourcemaps. Example, the TS repo references scripts in built/local/run.js, and built/local/tsserverlibrary.js

We will only bind the BP in a random one of these scripts.

In the TS case that prompted this, they don't actually load both scripts, but this prevents us from using an outFiles pattern like "built/local/**/*.js"
@roblourens roblourens added the bug label Mar 23, 2018
@roblourens roblourens self-assigned this Mar 23, 2018
Shenniey pushed a commit to Shenniey/vscode-chrome-debug-core that referenced this issue Oct 11, 2018
@roblourens
Fix microsoft#315 - Add mapping for create-react-app webpack:///src.
b5f01e9 
Wanted to add the ability to have multiple mappings for the same pattern and select one that matches what's on disk, but I don't actually like having that much smartness.
@roblourens roblourens mentioned this issue Apr 11, 2019
Closed
@rosen-vladimirov
Copy link

Hey guys,
Is there any update on this issue. Recently it is pretty easy to have the same file referenced in different source maps - just import the same file in two entry points of webpack compilation and you'll hit it. This breaks debugging in a really unexpected way.
Can we do something to handle this case? Is it planned for one of the next releases?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@roblourens roblourens

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roblourens @rosen-vladimirov