Nuxt config sourcemap option ignored

[IlyaSemenov]

Environment

• Operating System: Darwin
• Node Version: v16.15.0
• Nuxt Version: 2.16.0-27720022.54e852f
• Nitro Version: 0.6.1
• Package Manager: [email protected]
• Builder: webpack
• User Config: sourcemap, serverHandlers, devServerHandlers, typescript, bridge, buildModules
• Runtime Modules: -
• Build Modules: (), @nuxt/[email protected]

Reproduction

https://github.com/IlyaSemenov/nuxt-bridge-sourcemap-ignored

Describe the bug

The sourcemap option in nuxt config is completely ignored, both as an object or as a boolean.

Example:

export default defineNuxtConfig({
  sourcemap: { server: false, client: true },
})

nuxi build still generates server source map and doesn't generate client source map.

Additional context

The option is advertised by @nuxt/[email protected] which is a direct dependency of @nuxt/bridge:

  /**
   * Whether to generate sourcemaps.
   * 
   * @version 3
  */
  sourcemap: boolean | { server?: boolean, client?: boolean },

Logs

No response

[danielroe]

(This option was introduced in Nuxt 3 and never added to Bridge. You should see the @version 3 tag which indicates it's currently v3 only.)