fix: add production export condition to commands

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#15215

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

As we trace dependencies via the production export condition, if users do not run their node output with that condition, it may cause issues for them. We may add the condition to our documentation and preview commands to prevent these issues (and possibly overall increase performance).

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #605 (6ec410c) into main (400c176) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     nuxt/bridge#212   +/-   ##
=======================================
  Coverage   66.10%   66.10%           
=======================================
  Files          55       55           
  Lines        4116     4116           
  Branches      445      445           
=======================================
  Hits         2721     2721           
  Misses       1391     1391           
  Partials        4        4           

Impacted Files	Coverage Δ
src/presets/node-cli.ts	100.00% <100.00%> (ø)
src/presets/node-server.ts	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[pi0]

This really only solves the manual/preview commands. Production deployments rely on server.mjs are still affected.

[danielroe]

Production deployments should be launched with the condition as well.

[pi0]

Is there an argument or option for example for vercel to do it?

[danielroe]

I'm not sure. I'll follow up with them directly. But I would guess that setting a NODE_OPTIONS environment variable would allow it to be done.

[danielroe]

... and I believe we can do that from the FS API. Will check. Shall I add to this PR or make a separate one?

[pi0]

Indeed we may find solutions per (some) providers too. My point is, probably right solution instead of requiring the condition is to rewrite written package.json exports to make production default. We are already doing copy it is not that hard and is a universal fix.

[danielroe]

Sounds like a good idea 👍

[pi0]

I think we can rework this with new externals plugin and fine-gained access to package.json writing. #844 (feel free to pick it)