Nuxt dev-server recipe (auto-detect fallback)

Loaded when detect-project-type.sh returns nuxt and the startup tuple still lacks a command.

Signature

• nuxt.config.js, nuxt.config.mjs, or nuxt.config.ts exists
• package.json contains a nuxt dependency

Start command

Standard:

npm run dev

Also valid (read package.json scripts to confirm which the project uses):

pnpm dev
yarn dev
bun run dev

Prefer the package manager indicated by the lockfile:

• pnpm-lock.yaml -> pnpm dev
• yarn.lock -> yarn dev
• bun.lock / bun.lockb -> bun run dev
• package-lock.json or none -> npm run dev

Port

Default: 3000. Nuxt respects --port <port> and the PORT env var. Overrides follow the cascade in references/dev-server-detection.md.

Stub generation

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Nuxt dev",
      "runtimeExecutable": "npm",
      "runtimeArgs": ["run", "dev"],
      "port": 3000
    }
  ]
}

Substitute the resolved package manager (npm / pnpm / yarn / bun) and port.

Common gotchas

• Nitro server engine: Nitro (Nuxt's server engine) adds its own dev server behind Nuxt's; polish only cares about the Nuxt port. Do not probe the Nitro internal port separately.
• Port auto-increment: Nuxt may move to another port when 3000 is occupied. If the resolved URL does not answer, use the server log to let the user correct the start configuration.
• Nuxt 3 vs Nuxt 2: Nuxt 3 uses nuxt.config.ts, Nuxt 2 uses nuxt.config.js -- both are detected by the signature check. The dev-server command and port defaults are the same across both versions.