Don't strip stack traces of evaluated webpack bundles #1050
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
formatWebpackMessages
is neat! I'm using it outside ofcreate-react-app
. However, it's a little too eager in stripping stack traces from messages.I'm using the static-react-render-webpack-plugin which evaluates the outputted webpack bundle. When evaluating the outputted webpack bundle throws (in the user's code), the user needs the stack trace to debug what went wrong.
formatWebpackMessages
is stripping all stack traces making that difficult.This PR excludes stack traces where the source path contains
webpack:
. I've created a demo of the regexp working which shows stack traces being stripped forbabel-loader
but notstatic-react-render-webpack-plugin
.Example stack trace