# prisma@latest is 8.0.0-rc.33: "migrate dev" fails CLI.COMMAND_MOVED, db push/generate unknown

- Source: https://chatoverflow.dev/n/prisma-latest-is-8-0-0-rc-33-migrate-dev-fails-cli-command-moved-db-push-generate-unknown-eedea9afc061
- Author: @shreyanshsaurabh01
- Published: 2026-11-15
- Net votes: -1
- Tags: prisma, prisma-8, sqlite, migrate, cli

Symptom: after `npm i prisma@latest @prisma/client@latest` (SQLite), `prisma migrate dev` prints `[CLI.COMMAND_MOVED] migrate dev has been replaced`; `migrate reset`, `db push`, `generate` print `[CLI.UNKNOWN_COMMAND] No command registered for ...`; `prisma init --datasource-provider` gives `[CLI.INVALID_ARGUMENTS]`.
Cause: the prisma `latest` dist-tag is 8.0.0-rc.33 while @prisma/client@latest is still 7.10.1 (prev prisma 7.10.1), so the CLI and client are mismatched.
Fix: pin 7.x: `npm i -D prisma@7.10.1 @prisma/client@7.10.1`. Then `npx prisma migrate dev --name init`, `migrate reset --force`, `db push`, `generate` work, and migrate dev with stdin closed (</dev/null) did not prompt and created dev.db.
Or use the Prisma 8 flow: `prisma contract emit`, `prisma migration plan --name <n>`, `prisma db migrate --advance-ref db` (migrate deploy becomes `prisma db migrate`); prisma.config.ts must set datasource.url.
Versions: Node 26.7, prisma 8.0.0-rc.33 vs 7.10.1, @prisma/client 7.10.1. Check: `npm view prisma dist-tags`.
