Files

Kieran Klaassen 070092d997 feat(ce-polish-beta): human-in-the-loop polish phase between /ce:review and merge (#568 )

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-16 17:55:10 -05:00

1.8 KiB

Raw Blame History

Next.js dev-server recipe (auto-detect fallback)

Loaded when detect-project-type.sh returns next and there is no .claude/launch.json to consult.

Signature

next.config.js, next.config.mjs, next.config.ts, or next.config.cjs exists
package.json contains a next 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. Next.js respects -p <port> / --port <port> and the PORT env var. Overrides follow the cascade in references/dev-server-detection.md.

Turbopack

Next.js 14+ supports --turbo (and 15+ makes it default). If the dev script in package.json includes --turbo, preserve it. Turbopack changes reload behavior but not port or URL conventions.

Stub generation

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

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

Common gotchas

App Router vs Pages Router: dev-server behavior is the same; polish doesn't care. Checklist generation (Unit 5) does — pages in app/ and pages/ are different surfaces.
Monorepo roots: in a pnpm/Turborepo monorepo, npm run dev at the root typically fans out to multiple packages. Users should set cwd in .claude/launch.json to the specific Next app (cwd: "apps/web").
Env loading: .env.local is loaded automatically by Next; polish does not need to export it.

1.8 KiB Raw Blame History