NITRO0014Replace Nitro 2 package imports

Why it happens

Nitro 3 publishes the nitro package and a smaller public export map, so Nitro 2 package names and removed subpaths no longer resolve.

Fix

Import from nitro and its documented Nitro 3 public subpaths. Use nitro/builder for the old builder entry points.

Example

Use the Nitro 3 package name

Before

import { defineNitroConfig } from "nitropack/config"

After

import { defineConfig } from "nitro"

Verify the fix

Run only this rule after editing so the report stays focused on the diagnostic you are closing:

pnpm vite-doctor . --framework nitro --rules nitro/migration/no-v2-imports

Useful links

• Upstream docs

Related rule

• nitro/migration/no-v2-imports