Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Analyzing bundles with source-map-explorer doens't work

See original GitHub issue

Is this a bug report?

yes

Did you try recovering your dependencies?

yes

Which terms did you search for in User Guide?

analyze

Environment

Environment Info: System: OS: Windows 10 CPU: x64 Intel® Core™ i7-8550U CPU @ 1.80GHz Binaries: Yarn: 1.9.2 - C:\Program Files (x86)\Yarn\bin\yarn.CMD npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: 42.17134.1.0 Internet Explorer: 11.0.17134.1 npmPackages: react: ^16.7.0 => 16.8.5 react-dom: ^16.7.0 => 16.8.5 react-scripts: ^2.1.5 => 2.1.8 npmGlobalPackages: create-react-app: Not Found

Steps to Reproduce

create a typescript CRA project
create components.
Divide them to various apps/sub projects.
Render apps conditionally, using React.lazy and Suspense
Follow instructions on https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size a. npm install --save source-map-explorer b. add "analyze": "source-map-explorer 'build/static/js/*.js'" to scripts. c. run “npm run build” followed by “npm run analyse”.

Actual Behavior

Error: No file(s) found

Issue Analytics

State:
Created 4 years ago
Reactions:3
Comments:13 (2 by maintainers)

Top GitHub Comments

14reactions

mistereechapmancommented, Apr 23, 2019

If the documentation is updated to remove the single quotes from the path then this will work.

7reactions

mistereechapmancommented, Apr 24, 2019

For any windows users running into the same issue try removing the quotes. Even when trying the npx workaround also I ran into the same issues until I removed the quotes.

node : V11.10.1 npm : 6.7.0