Nuxt config sourcemap option ignored

Environment

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

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/schema@3.0.0-rc.12 which is a direct dependency of @nuxt/bridge:

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

Logs

No response

Start with the linked reproduction repository and run nuxi build using the shown sourcemap configuration. Trace how the Nuxt config is handled by the webpack builder, then verify that server maps are disabled and client maps are generated for both boolean and object forms.