-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
NODE_ENV explicitly specified #23402
Comments
cc: @pi0 It seems we have a regression with tracing export conditions as the Vue dev build is also getting picked. reproduction from linked issue: https://stackblitz.com/edit/nuxt-examples-tnmdbb?file=package.json. |
Checking reproduction, it seems that On vue side, we had been tracing it for a long time for supporting For a solution in Nitro we can:
|
This is now resolved (for vue) in the latest release of See bundle size diff in https://github.com/nuxt/nuxt/pull/25036/files#diff-04a7585c5d6ddd5cf80321c69bc6e07cd85e9e86ae35fa5f9c036651f137c312. |
Describe the feature
I have experienced that when running a build project using
node ./.output/server/index.mjs
vue.js was running in dev mode, because if you don't defineNODE_ENV=production node ./.output/server/index.mjs
, then you will get a dev build of vue.js (by default) https://github.com/vuejs/core/blob/main/packages/runtime-core/index.jsDo you think it is necessary to add this note to the doc? (https://nuxt.com/docs/getting-started/deployment#nodejs-server)
Additional information
Final checks
The text was updated successfully, but these errors were encountered: