NestJS CLI says the @nestjs/schematics collection cannot be resolved
Collection "@nestjs/schematics" cannot be resolvedShort answer
The CLI looks for the schematics collection in node_modules and does not find the package. It is usually listed as a development dependency, so installs that skip dev dependencies, like NODE_ENV=production or --omit=dev, leave it out. Reinstall with dev dependencies where you run nest generate.
Fix it fast
1Find out which cause you have
Ask npm whether the package is installed in this project, and which environment settings might skip dev dependencies.
npm ls @nestjs/schematics echo "NODE_ENV=$NODE_ENV"2Match what you see, then jump to its fix
What does the error look like?
Collection "@nestjs/schematics" cannot be resolved
Cause 1 of 2
Dev dependencies were skipped during install
1Check
npm leaves out dev dependencies when NODE_ENV is production, or when you pass --omit=dev. @nestjs/schematics is the package behind nest new, nest generate and nest upgrade, so those commands fail when it is not there.
grep -n "schematics" package.json
npm config get omit2Fix
Install dev dependencies where you run Nest CLI commands, and keep the slim install for the final runtime image only.
npm install --include=dev
npx nest generate --help3Verify
The package shows up and the CLI loads.
npm ls @nestjs/schematics
npx nest generate --helpConfirmed by docs.npmjs.com
Cause 2 of 2
node_modules is missing or incomplete in this folder
1Check
npm install reads package.json and installs what it lists. Until it runs in this folder, the CLI cannot find the collection.
ls node_modules/@nestjs
ls package.json2Fix
Run the install in the project folder (the one that contains package.json), then retry the command.
npm install
npx nest generate --help3Verify
The folder exists and the CLI loads.
ls node_modules/@nestjs/schematicsConfirmed by docs.npmjs.com
How do I stop it coming back?
- Build in one stage with all dependencies, and copy only dist into the runtime stage.
- Use a Node.js version the Nest docs list for the CLI generators.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
Related fixes
Back end
The nest command is not found in the terminal
bash: nest: command not found
The shell cannot find a nest executable on its PATH.
3 causes, each with a fixBack end
TypeScript cannot find module '@nestjs/core' or its type declarations
error TS2307: Cannot find module '@nestjs/common' or its corresponding type declarations.
TS2307 means TypeScript searched node_modules and found neither the package nor its types.
3 causes, each with a fixBack end
Node.js in Docker Compose cannot reach MySQL on 127.0.0.1:3306
Error: connect ECONNREFUSED 127.0.0.1:3306
Inside a container, 127.0.0.1 is that container, not MySQL.
3 causes, each with a fixBack end
NestJS GraphQL cannot work out the output type of a field or query
Cannot determine a GraphQL output type for the "<name>". Make sure your class is decorated with an appropriate decorator.
In code-first mode Nest reads TypeScript types through decorators, and arrays, promises and unions disappear at runtime.
2 causes, each with a fixBack end
IntelliJ IDEA breakpoints are ignored in a NestJS app
No 'Debugger listening' line appears when the NestJS app starts
IntelliJ can only debug a NestJS app when the Node.js process runs with the inspector on and the IDE attaches to its port.
4 causes, each with a fixBack end
NestJS watch mode does not restart after I save a file
Changes show on the host but not in the running container
Watch mode only sees files that exist inside the process that runs it.
3 causes, each with a fix