Error: Collection "@nestjs/schematics" cannot be resolved.

[radagva]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When trying to create a fresh nestjs project it fails showing this error

Error: Collection "@nestjs/schematics" cannot be resolved.

Failed to execute command: node node "$HOME/Library/pnpm/store/v11/links/@angular-devkit/schematics-cli/19.2.27/328503cc1d656a5a7b6a1584df936ba36c4a16f6043991da97bbe9a24d4106d7/node_modules/@angular-devkit/schematics-cli/bin/schematics.js" @nestjs/schematics:application --name=example --directory=undefined --no-dry-run --no-skip-git --no-strict --package-manager="pnpm" --collection="@nestjs/schematics" --language="ts"

If I run pnpm dlx @nestjs/cli new example it works as expected. This error only happens to me when using the installed CLI.

Minimum reproduction code

This error happens while creating a project with the installed CLI

Steps to reproduce

1. pnpm --global install @nestjs/cli
2. nest new example.
3. select pnpm as package manager to install dependencies.
4. Error.

Expected behavior

After running nest new example and selecting a package manager to install dependencies it should simply install dependencies

Package version

11.0.23

NestJS version

11.1.27

Node.js version

24.15.0

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

pnpm version: 11.8.0

[micalevisk]

What about using this instead:

npx @nestjs/cli new example

?

[radagva]

@micalevisk it works if I use npx, also works if I use pnpm dlx, the only way it doest not work is if I use the local nest command from @nestjs/cli as nest new example

The other nest commands like nest g module|controller|guard seems to work, the only command that is not working locally for me is new

[micalevisk]

I didnt manage to reproduce it in my linux but I did reproduce it in my MacOS, this is why I dont recomment installing the CLI globally :/

[radagva]

How do you recommend it? Like pnpm dlx new ... and then having maybe a "generate" script in the package json pointing to the nest schematics? Or maybe don't use the schematics at all?

[micalevisk]

my flow is: always use npx @nestjs/cli@latest .../pnpm dlx @nestjs/cli@latest ... to create a new project. And then, within the project (same dir as the package.json), use the npx nest .../pnpm nest .../yarn nest ... approach so that it will use the locally installed nestjs's CLI.

I really don't see the benefits on using the globally installed CLI as nestjs's version of the project will likely to be different from project to project

[micalevisk]

from what I tested on MacOS, this is broken since @nestjs/cli@9.0.0 (perhaps even before this)