Error when Analyzing bundle (source-map-explorer).
See original GitHub issueI would like to point out an issue I am facing. I followed the exact steps in this docs but unfortunately when I try to run npm run analyze
it gives the following error:
npm run analyze
> tic-tac-toe@0.1.0 analyze
> source-map-explorer build/static/js/*.js
build/static/js/main.0e109ef0.js
You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer
npm run build
was successful.
Can anyone look into this please.
Thanks!
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
source-map-explorer - npm
Possible error codes are: Unknown; NoBundles - Empty array is passed to explore; OneSourceSourceMap - Bundle source map only contains one source ...
Read more >Analyzing Angular bundle with Source Map Explorer
The source map explorer determines which file each byte in your minified code came from. It shows you an interactive tree-map visualization to ......
Read more >source-map-explorer error: Check that you are using the ...
This answer is based on @piecioshka's ~ but disables column/line mapping check, as indicated in this source-map-explorer#README.
Read more >TIL: Analyzing Angular App's Bundle Size with source-map ...
One way to solve this issue is to tell Angular CLI to put vendor scripts in the main bundle file by setting --vendor-chunk...
Read more >Angular bundle optimization using Webpack Bundle analyzer ...
We take a look at two tools - Webpack Bundle analyzer/ Sourcemap explorer - which can be used to optimize generated js bundle...
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
This is how I got it to work in
package.json
:I get this error when running
react-scripts start
.