Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Better logging
See original GitHub issueReally want improve logging. Seems like it is inevitable that we drop react-dev-utils/formatWebpackMessages and use a custom formatter. This would allow us to have one call to
const multiCompilers = compile([serverConfig, clientConfig])
In multi-compiler mode, we can still pass the respective clientCompiler to webpack-dev-server and watch the serverCompiler in pretty much the same way. However, we would then be able to write truly universal logger (which would look a lot like formatWebpackMessages, but handle multiple configs).
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Razzle Loading/Compiling … (probably powered by Ora)
Razzle Errors pipe below:
Nope. Go for it!
I was talking to Sean Larkin at React Rally about Webpack and unfortunately there is literally zero way to tell if the errors are identical or not. So despite the current logger, we really should be showing both at all times.