Source map errors
See original GitHub issueI’m getting this error as of the latest release from webpack:
Chrome 53.0.2785 (Linux 0.0.0) ERROR
Uncaught SyntaxError: Unexpected identifier
at webpack:///source/src/prepare/webgl/WebGLPrepare.js:277:0 <- config/spec-bundle.js:58543
Chrome 53.0.2785 (Linux 0.0.0) ERROR
Uncaught SyntaxError: Unexpected identifier
at webpack:///source/src/prepare/webgl/WebGLPrepare.js:277:0 <- config/spec-bundle.js:58543
I had a look at that line and it looks fine… really strange that this is suddenly an issue. Will debug some more.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Source map errors — Firefox Source Docs documentation
The source map data can be invalid — either not a JSON file at all, or with an incorrect structure. Typical error messages...
Read more >4 Reasons Why Your Source Maps are Broken
4 Reasons Why Your Source Maps are Broken · Missing or incorrect source map directive · Missing original source files · Bad source...
Read more >How to prevent Firefox DevTools from showing "Source ...
You can disable source maps globally by going into the Toolbox Options of the Developper Tools and unchecking Enable Source Maps .
Read more >Source map support for JavaScript error analysis
Analyze a JavaScript error using a source map · In the Dynatrace menu, go to Web, and select the application that you want...
Read more >Source Map Troubleshooting
Sometimes source maps can be generated with no content in them, or in an invalid format, e.g. base64. Check the source maps that...
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

Ignoring the source maps for pixi fixed it, so I think something’s wrong with the pixi sourcemaps
As of the latest release (4.0.2 vs 4.0.1):