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

Source map doesn't analyze #7938

Closed
carpben opened this issue Nov 6, 2019 · 3 comments
Closed

Source map doesn't analyze #7938

carpben opened this issue Nov 6, 2019 · 3 comments

Comments

@carpben
Copy link
Contributor

carpben commented Nov 6, 2019

Describe the bug

In a CRA3 typescript project, source-map-explorer fails to analyze parts of build/bundles, and displays them as null.
A few days ago, still using CRA2 it worked well.

Did you try recovering your dependencies?

Yes
npm --version : 6.13.0

Terms I searched for:

source-map-explorer typescript CRA Create-React-App 3 null

I am aware of #6994, but his solution requires ejecting.

Environment

System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Binaries:
Yarn: 1.9.2 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.13.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.387.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: ^16.8.6 => 16.11.0
react-dom: ^16.8.6 => 16.11.0
react-scripts: ^3.2.0 => 3.2.0
npmGlobalPackages:
create-react-app: Not Found

Steps to reproduce

  1. CRA 3 --typescript project
  2. In package.json
"scripts": {
    "analyze": "source-map-explorer build/js-bundles/*.js",
  },
  1. npm run analyze

Actual behavior

(Write what happened. Please add screenshots!)
image

Expected behavior

Instead of null, display file names from source code.

@carpben
Copy link
Contributor Author

carpben commented Nov 6, 2019

A similar issue has been opened on source-map-explorer, and it seems a few users of CRA have been suffering from it after the release of CRA3 [link].

@stale
Copy link

stale bot commented Dec 6, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

@stale stale bot added the stale label Dec 6, 2019
@stale
Copy link

stale bot commented Dec 11, 2019

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.

@stale stale bot closed this as completed Dec 11, 2019
@lock lock bot locked and limited conversation to collaborators Dec 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant