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

Jump to bottom

Remove Windows note for source-map-explorer #2719

Merged
merged 1 commit into from Jul 3, 2017
Merged

Remove Windows note for source-map-explorer #2719

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 0 additions & 10 deletions packages/react-scripts/template/README.md
View file
Open in desktop
Expand Up @@ -1671,16 +1671,6 @@ Then in `package.json`, add the following line to `scripts`:
"test": "react-scripts test --env=jsdom",
```

>**Note:**
>
>This doesn't quite work on Windows because it doesn't automatically expand `*` in the filepath. For now, the workaround is to look at the full hashed filename in `build/static/js` (e.g. `main.89b7e95a.js`) and copy it into `package.json` when you're running the analyzer. For example:
>
>```diff
>+ "analyze": "source-map-explorer build/static/js/main.89b7e95a.js",
>```
>
>Unfortunately it will be different after every build. You can express support for fixing this on Windows [in this issue](https://github.com/danvk/source-map-explorer/issues/52).

Then to analyze the bundle run the production build then run the analyze
script.

Expand Down