fix(nuxt): don't disable scripts in dev mode with experimental noScripts

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#15000

❓ 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

We should only respect experimental.noScripts in built mode.

📝 Checklist

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

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt3-docs ready!

Name	Link
🔨 Latest commit	57c7382
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/632c17e8f3a2610008869926
😎 Deploy Preview	https://deploy-preview-7745--nuxt3-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[pi0]

Doesn't it make sense to have consistent behavior between dev and prod for disabling scripts?

[danielroe]

We are testing for dev here:

framework/packages/nuxt/src/core/nuxt.ts

Line 95 in 5605f1c

if (nuxt.options.experimental.noScripts && !nuxt.options.dev) {

I think HMR for dev, but no scripts for built site seems a better default, but happy to be convinced otherwise.