E8007

With features.noScripts: 'production' (the default when noScripts is enabled), scripts are only stripped from rendered HTML in production builds. In development the page still ships JavaScript, so behaviour that depends on it (lazy hydration strategies, nuxt-client components inside server components) appears to work in dev and then silently breaks after deployment.

This warning is emitted during development when a rendered route uses one of these features.

Resolution

Either remove the client-side dependency from the affected route, or scope script stripping to the routes that are genuinely static using the noScripts route rule (which applies in development too, so any breakage is visible immediately):

export default defineNuxtConfig({
  routeRules: {
    '/static/**': { noScripts: true },
  },
})

Alternatively, set features.noScripts: 'all' to strip scripts in development as well, making the production behaviour observable in dev.