Source map warnings
See original GitHub issueUsing this library I’m getting warnings like these in browser console and webpack dev server output. I’m using typescript in my project. Do you know if there’s something I could do to prevent these warnings?
./node_modules/web-streams-polyfill/dist/polyfill.min.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from 'C:\Users\vinca\Documents\Code\proton-drive\node_modules\web-streams-polyfill\src\lib\abort-signal.ts' file: Error: ENOENT: no such file or directory, open 'C:\Users\vinca\Documents\Code\proton-drive\node_modules\web-streams-polyfill\src\lib\abort-signal.ts'
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
DevTools failed to load SourceMap: Could not load content for...
For many of my js files I have no source map. When using the devtools console it pollutes the warnings about that. I...
Read more >After Upgrading to CRA 5.0 getting a lot of: Failed to parse ...
The warnings are correct. These packages source maps pointing to src that is not included in the package. The solution would be to...
Read more >Browser console shows DevTools failed to load SourceMap ...
Solution · Go to the developer tools (F12 in the browser); · Select the Cogwheel in the upper right corner; · In the...
Read more >Failed to parse source map warnings - Dynamic Docs
Failed to parse source map warnings ... If using create-react-app v5, you may see some warnings (although they appear like errors) when running/building...
Read more >Warning: -file- is being assigned a //# sourceMappingURL, but ...
A source map has been specified more than once for a given JavaScript source. JavaScript sources are often combined and minified to make...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hang on, something is wrong indeed with the polyfill’s source maps! Each entry in the
sourcesContentarray isnull! 🤯 (See the file on unpkg.com)I think I didn’t notice at first because I did
git checkout v2.1.1 && npm install. However, since I already had newer versions of Rollup and its plugins installed onmaster, it may not have downgraded them? I just tried it again locally by runningnpm ciinstead, and I can now reproduce the broken source maps.I also tried building the tip of
masterand using that inside of the test project, and that works: the new source map has proper source contents. So you can expect the next release to fix the problem. 🙂If it’s okay for you, I’ll wait until the 3.0.0 release to ship this fix. For the time being, you can use your
excludeworkaround. Sorry about the inconvenience!Version 3.0.0 has been released, with working source maps this time. 😁