-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go to implementations won't work when sourcesContent present in *.map #142980
Comments
Please provide a minimal example project and steps to reproduce this issue /needsMoreInfo |
It seems sourcesContent have higher priority over sources. So when it presents, vs code won't go to the original files. You can add this property to any map file, then Go to Implementation will stop work. |
Please share a project that demonstrates this issue so we can investigate it |
In my demo, I use an empty sourcesContent string, but you can use the right string, the result is the same. |
Ok, that sounds like a duplicate of microsoft/TypeScript#6209 based on your description Closing as upstream |
Does this issue occur when all extensions are disabled?: Yes
Reproduce:
When I serve angular app, it will somehow add sourcesContent in my angular libraries' *.map files. Then Go to implementations won't work, even sources is still there. If I reinstall those packages, and right before I run
ng serve
, it will work again. It will even work, if I just manually delete sourcesContent.The text was updated successfully, but these errors were encountered: