fix(nuxt): disable x-nuxt-no-ssr header by default

[danielroe]

🔗 Linked issue

resolves #15667

❓ 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)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

We have an undocumented header for disabling SSR responses, x-nuxt-no-ssr. I think it would be better not to have this enabled by default as it allows third-parties to control the behaviour of the Nuxt renderer.

I think we can consider this a non-breaking change if clearly signposted in release notes.

👉 Migration

If you were using the x-nuxt-no-ssr flag, you can turn on the previous behaviour with:

export default defineNuxtConfig({
  experimental: {
    respectNoSSRHeader: true
  }
})

📝 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

[pi0]

LGTM in general to make ssr behavior more predictable