-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(react): fix conflicting NODE_ENV values between an application an… #9460
fix(react): fix conflicting NODE_ENV values between an application an… #9460
Conversation
…d webpack Plugins (DefinePlugin) ISSUES CLOSED: nrwl#7924
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/8qFwYSAHzw1zuA7tm8gz4jYHwzKR |
LGTM |
const isScriptOptimizeOn = | ||
typeof options.optimization === 'boolean' | ||
? options.optimization | ||
: options.optimization && options.optimization.scripts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be possible to be shortened and simplified:
typeof options.optimization === 'boolean'
? options.optimization
: options.optimization?.scripts || false
Has this been released yet? |
Not yet, @nemonemi. 13.9.4 was released before this fix was merged. 13.9.5 should include this fix. |
Any idea when this will be released? looking for a fix to this issue! |
This issue has not been resolved with 13.9.5. |
I can confirm, the issue still remains on both existing apps and newly-generated apps. Verified that both global and local nx was on 13.9.5. Serving app on Windows still results in the following warning:
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Fix conflicting NODE_ENV values between an application and webpack Plugins (DefinePlugin)
ISSUES CLOSED: #7924
Current Behavior
Currently, serving a fresh Nx React application shows the following:
Expected Behavior
On freshly served applications there should be no such warning as stated above.
Related Issue(s)
Fixes #