Conflicting peer dependency: @swc/cli | NestJS | Page 1

hidden perch Jan 29, 2024, 2:09 AM

#

Generally, if you look at the documentation and install @swc-cli, it will install to the latest version.

npm i --save-dev @swc/cli @swc/core

https://docs.nestjs.com/recipes/swc#installation
The current version of @swc-cli is v0.3.5.
https://www.npmjs.com/package/@swc/cli?activeTab=versions

Currently, @nestjs/cli has a peer dependency of ^0.1.62, which causes crashes like the one in the capture image.

https://github.com/nestjs/nest-cli/blob/24b2b1a6be9d800d312603275128f9df7a3c498e/package.json#L93-L96

In this case, should we modify the installation instructions in the documentation to @swc/[email protected] or should we modify the dependency of @nestjs/cli?

kind mulch Jan 29, 2024, 12:00 PM

#

you should wait for this PR to get merged: https://github.com/nestjs/nest-cli/pull/2467
or just force the installation if you know that that version is compatible with @nestjs/cli already

GitHub

chore(deps): update swc monorepo by renovate[bot] · Pull Request #2...

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@swc/cli
^0.1.62 -> ^0.1.62 || ^0.3.0

@swc/cli
0.1.65 -> 0.3.5

@swc/core (source)
1.3...

hidden perch Jan 30, 2024, 1:33 AM

#

kind mulch you should wait for this PR to get merged: https://github.com/nestjs/nest-cli/pu...

Thanks for your reply.
FYI, the paths when building from @swc/cli v0.3.x behave differently than previous versions, so I think you should consider the stripLeadingPaths option in @swc/[email protected] in nest-cli for consistent behavior.

Reference links

https://github.com/swc-project/cli/issues/281

https://github.com/swc-project/cli/pull/283

https://github.com/swc-project/cli/issues/282#issuecomment-1911862535

#Conflicting peer dependency: @swc/cli