Remove Modules

  • Remove @nuxt/nitro: Bridge injects same functionality

Update Config

import { defineNuxtConfig } from '@nuxt/bridge'

export default defineNuxtConfig({
  bridge: {
    nitro: true

Update Your Scripts

You will also need to update your scripts within your package.json to reflect the fact that Nuxt will now produce a Nitro server as build output.

Install Nuxi

Install nuxi as a development dependency:

yarn add --dev nuxi
npm install -D nuxi


Nuxt 3 introduced the new Nuxt CLI command nuxi. Update your scripts as follows to leverage the better support from Nuxt Bridge:

  "scripts": {
-   "dev": "nuxt",
+   "dev": "nuxi dev",
-   "build": "nuxt build",
+   "build": "nuxi build",
-   "start": "nuxt start",
+   "start": "nuxi preview"

If nitro: false, use the nuxt2 command.

Static Target

If you have set target: 'static' in your nuxt.config then you need to ensure that you update your build script to be nuxi generate.

  "scripts": {
    "build": "nuxi generate"

Server Target

For all other situations, you can use the nuxi build command.

  "scripts": {
    "build": "nuxi build",
    "start": "nuxi preview"

Exclude Built Nitro Folder From Git

Add the folder .output to the .gitignore file.

Ensure Everything Goes Well

鉁旓笍 Try with nuxi dev and nuxi build (or nuxi generate) to see if everything goes well.