Replies: 2 comments 2 replies
-
had a teammate complain about build speeds in development and I was surprised to find the devtool is reverted by next I ended up patching nextjs package (using yarn patch protocol) with the following line commented in
then in next.config.js we set devtool from env:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Workaround: export default {
webpack(config) {
Object.defineProperty(config, 'devtool', {
get() {
return 'source-map';
},
set() {},
});
return config;
},
}; You'll still see |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the feature you'd like to request
Change the functionality that leads to this terminal output:
There are many uses for various webpack
devtool
configurations outside of "eval-source-map" and having the option to change them without Next overriding an explicit configuration choice would be greatly appreciated.Specifically, the
eval
option allows for an incredible amount of additional information when setting breakpoints in a browser's developer tools.I understand the possibility of "severe performance regressions", but I think a warning (maybe a louder warning) is sufficient.
Describe the solution you'd like
Do not override the
devtool
webpack setting in development when explicitly configured.Describe alternatives you've considered
Continuing with Next and accept a vastly less efficient debugging workflow.
Beta Was this translation helpful? Give feedback.
All reactions