-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Failed to parse source map #437
Comments
More info:
|
https://www.npmjs.com/package/source-map-loader#user-content-examples Some popular packages do not provide sourcemap files, which is normal, and you can configure to ignore warnings for these packages. @JEMasonMedia https://webpack.js.org/configuration/other-options/#ignorewarnings |
I must be missing something. I just installed the library and set up the config file, but nothing changed once I restarted the app. I used create-react-app to bootstrap my app. Could you possibly provide a little more info please? |
@JEMasonMedia I don't know why you have this error, I can't reproduce your error. |
How to reproduce:
import the library into App.js:
Those warnings will appear in the console. |
I reproduced this problem. I've been using my own tools. This issue was ignored. |
"scripts": {
- "start": "react-scripts start",
+ "start": "GENERATE_SOURCEMAP=false react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
}, |
It was fixed by adding |
'GENERATE_SOURCEMAP' is not recognized as an internal or external command, .env? |
"scripts": { |
Finally googled what you were saying and got the .env workaround to work. Thank you for helping me out! |
If you are running on Windows, you need to use the compatible tool npm install --save-dev cross-env "start": "cross-env GENERATE_SOURCEMAP=false react-scripts start", @JEMasonMedia Of course, the way to use |
The .env worked on its own in windows 11. Thank you very much for your help. |
For whatever reason, I am getting the below parse warning. It has nothing to do with my code as it only appears when I "import MDEditor from '@uiw/react-md-editor'" The library still seems to work fine, but I am not sure what to do about these major warnings.
The text was updated successfully, but these errors were encountered: