DocsUpgrade GuideMigrate to Nuxt Bridge
Configuration
Learn how to configure Nuxt Bridge to your own needs.
Feature Flags
You can optionally disable some features from bridge or opt-in to less stable ones. In normal circumstances, it is always best to stick with defaults!
You can check bridge/src/module.ts for latest defaults.
nuxt.config.ts
import { defineNuxtConfig } from '@nuxt/bridge'export default defineNuxtConfig({ bridge: { // -- Opt-in features -- // Use Vite as the bundler instead of webpack 4 // vite: true, // Enable Nuxt 3 compatible useHead // meta: true, // -- Default features -- // Use legacy server instead of Nitro // nitro: false, // Disable Nuxt 3 compatible `nuxtApp` interface // app: false, // Disable Composition API support // capi: false, // ... or just disable legacy Composition API support // capi: { // legacy: false // }, // Do not transpile modules // transpile: false, // Disable <script setup> support // scriptSetup: false, // Disable composables auto importing // imports: false, // Do not warn about module incompatibilities // constraints: false }, vite: { // Config for Vite }})Migration of each option
router.base
export default defineNuxtConfig({- router: {- base: '/my-app/'- }+ app: {+ baseURL: '/my-app/'+ }})build.publicPath
export default defineNuxtConfig({- build: {- publicPath: 'https://my-cdn.net'- }+ app: {+ cdnURL: 'https://my-cdn.net'+ }})