Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package Conflict between Angular 19 and NestJS #29409

Open
1 of 4 tasks
phihochzwei opened this issue Dec 19, 2024 · 2 comments
Open
1 of 4 tasks

Package Conflict between Angular 19 and NestJS #29409

phihochzwei opened this issue Dec 19, 2024 · 2 comments

Comments

@phihochzwei
Copy link

Current Behavior

After migrating to NX 20.2.2 (aside from problems with the eslint migrations) I am facing the problem that I no longer can run npm ci due to a package conflict

npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: @angular-devkit/[email protected] npm error Found: [email protected] npm error node_modules/chokidar npm error peerOptional chokidar@"^3.5.2" from @angular-devkit/[email protected] npm error node_modules/@nx/nest/node_modules/@angular-devkit/core npm error @angular-devkit/core@"16.0.1" from @angular-devkit/[email protected] npm error node_modules/@nx/nest/node_modules/@angular-devkit/schematics npm error @angular-devkit/schematics@"16.0.1" from @nestjs/[email protected] npm error node_modules/@nx/nest/node_modules/@nestjs/schematics npm error @nestjs/schematics@"^9.1.0" from @nx/[email protected] npm error node_modules/@nx/nest npm error @angular-devkit/core@"16.0.1" from @nestjs/[email protected] npm error node_modules/@nx/nest/node_modules/@nestjs/schematics npm error @nestjs/schematics@"^9.1.0" from @nx/[email protected] npm error node_modules/@nx/nest npm error dev @nx/nest@"20.2.2" from the root project npm error chokidar@"^3.5.3" from [email protected] npm error node_modules/@storybook/builder-webpack5/node_modules/fork-ts-checker-webpack-plugin npm error fork-ts-checker-webpack-plugin@"^8.0.0" from @storybook/[email protected] npm error node_modules/@storybook/builder-webpack5 npm error @storybook/builder-webpack5@"8.4.7" from @storybook/[email protected] npm error node_modules/@storybook/angular npm error dev @storybook/angular@"8.4.7" from the root project npm error 6 more (@swc/cli, browser-sync, ...) npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error

I am no expert but to me it looks like the version of the nestJS Schematics in @nx/nest needs to be bumped to a higher version

Expected Behavior

npm ci runs smoothly :)

GitHub Repo

No response

Steps to Reproduce

Nx Report

Node           : 22.6.0
OS             : darwin-arm64
Native Target  : aarch64-macos
npm            : 10.8.2

nx                     : 20.2.2
@nx/js                 : 20.2.2
@nx/jest               : 20.2.2
@nx/eslint             : 20.2.2
@nx/workspace          : 20.2.2
@nx/angular            : 20.2.2
@nx/cypress            : 20.2.2
@nx/devkit             : 20.2.2
@nx/eslint-plugin      : 20.2.2
@nx/module-federation  : 20.2.2
@nx/nest               : 20.2.2
@nx/node               : 20.2.2
@nx/plugin             : 20.2.2
@nx/storybook          : 20.2.2
@nx/web                : 20.2.2
@nx/webpack            : 20.2.2
typescript             : 5.6.3
---------------------------------------
Registered Plugins:
@nx/storybook/plugin
---------------------------------------
Community plugins:
@ngrx/component      : 18.1.1
@ngrx/effects        : 18.1.1
@ngrx/entity         : 18.1.1
@ngrx/router-store   : 18.1.1
@ngrx/schematics     : 18.1.1
@ngrx/signals        : 18.1.1
@ngrx/store          : 18.1.1
@ngrx/store-devtools : 18.1.1
@storybook/angular   : 8.4.7
ng-mocks             : 14.13.1
ng2-charts           : 6.0.1
---------------------------------------
Local workspace plugins:
         @deich-lib/workspace-plugin

Failure Logs

Package Manager Version

No response

Operating System

  • macOS
  • Linux
  • Windows
  • Other (Please specify)

Additional Information

No response

@skyleguy
Copy link

i am seeing this same issue unfortunately

@skyleguy
Copy link

Has anyone figured out any potential work around? I was excited to see my migrate to angular 19 succeed but then surprised when I tried to run npm I after the successful migrations that there were package issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants