You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should warn very loudly (or even refuse to build) when the user disables minification for a production build. I think it's best to start with a warning.
We need to check for minimize to be false, or an empty minifier array.
Follow-up: what other properties would be good to ensure users aren't configuring by accident?
The text was updated successfully, but these errors were encountered:
I would love to have separate warnings for optimization.minimize and optimization.minifiers. The former is worse since it also disables Webpack's optimizations for NODE_ENV, module concatenation, tree shaking etc.
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 31, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should warn very loudly (or even refuse to build) when the user disables minification for a production build. I think it's best to start with a warning.
We need to check for minimize to be false, or an empty minifier array.
Follow-up: what other properties would be good to ensure users aren't configuring by accident?
The text was updated successfully, but these errors were encountered: