Skip to content
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

Getting errors for packages without map file #572

Closed
ardymalihi opened this issue Jul 10, 2020 · 1 comment
Closed

Getting errors for packages without map file #572

ardymalihi opened this issue Jul 10, 2020 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)

Comments

@ardymalihi
Copy link

Describe the bug
Debugger listening on ws://127.0.0.1:49829/64048437-d258-42da-8303-cc959b970c65
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Could not read source map for file:///.../node_modules/@grpc/proto-loader/build/src/index.js: ENOENT: no such file or directory, open '/.../node_modules/@grpc/proto-loader/build/src/index.js.map'

Some third party packages have //# sourceMappingURL=index.js.map but cannot be found so as a result you will see lots of errors in the console.

The error makes sense because the map file should exist if sourceMappingURL is added at the end of js file but it hard to convince all the thirds party packages to include the map files to their projects :)

To Reproduce
Steps to reproduce the behavior:

  1. install any packages without map ie: @grpc/proto-loader
  2. import in your project file
  3. run debug
  4. See the error above ^^^^

Log File

Debugger listening on ws://127.0.0.1:49829/64048437-d258-42da-8303-cc959b970c65
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Could not read source map for file:///.../node_modules/@grpc/proto-loader/build/src/index.js: ENOENT: no such file or ...

@ardymalihi ardymalihi added the bug Issue identified by VS Code Team member as probable bug label Jul 10, 2020
@connor4312
Copy link
Member

Thanks for the issue and good steps. This duplicates microsoft/vscode#102042

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants