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
Angular 15 ng add dependency issue 'Packages installation failed' #942
Comments
Same problem here |
Any workaround for the time being? |
Had the same issue, did some investigation and after few hours seems like there is no support for Angular 15 which makes me quite sad considering Angular 15 has been out for some time now. Only workaround to this issue is to use latest Angular 14 deps and it will work with latest version of |
Hey folks, till the time the PR from bartlomiejgawel is not merged, you can use this NPM package: https://www.npmjs.com/package/ng-universal-15 This package supports Angular 15. PS. I used the PR of bartlomiejgawel and published my own package as a quick fix ;) |
I think this has been fixed in |
Let's track this here #943 |
I'm submitting a...
Current behavior
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: webapp@0.0.0
npm ERR! Found: @angular/common@15.0.2
npm ERR! @angular/common@"^15.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^12.0.0 || ^13.0.0 || ^14.0.0" from @nestjs/ng-universal@6.1.0
npm ERR! node_modules/@nestjs/ng-universal
npm ERR! @nestjs/ng-universal@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
ng add @nestjs/ng-universal
fails with ✖ Packages installation failed, see above.Expected behavior
NestJS is added to Angular 15 project.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Use the framework
Environment
The text was updated successfully, but these errors were encountered: