Closed rgembalik closed 1 year ago
Hi, take a look to this seems that it caused by CRA itself.
@LearningProcesss Yup, I am already tracking the topic at CRA, but the thing is it was reported some time ago and is not looking to be fixed soon. The solutions are mainly to disable source maps entirely (which sucks for development), make some modifications to configs of react scripts after the installation, or simply enable source maps on the target packages.
The thing is that source maps in packages are still useful to keep for debugging purposes, so I'd still see this as an improvement to this package.
It's not a critical bug, so I'd understand if you'll not wish to add them ;)
Any chance for source maps to be included in the npm package?
Currently, when used with React, I get a ton of warning messages like this:
While it's nothing substantial, it does obscure true errors if they appear in the CLI. Since I am using create-react-app (CRA), I have no way of changing the webpack config to ignore those messages, as there is no such option in CRA.