-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support for Angular 14 #172
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ... (check one with "x")
Current behavior
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^14.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@">=9.0.0 <10.0.0" from @ngx-config/[email protected]
npm ERR! node_modules/@ngx-config/core
npm ERR! @ngx-config/core@"*" 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.
npm ERR!
npm ERR! See C:\Users\Admin\AppData\Local\npm-cache\eresolve-report.txt for a full report.
Expected/desired behavior
Need to be install successfully
Minimal reproduction of the problem with instructions
In angular 14 Project, try npm i @ngx-config/core
What is the motivation / use case for changing the behavior?
To be able to use ngx-config with the most recent angular version
Environment
Angular version: 14.0.0
For Tooling issues:
Node version: v16.13.1
Platform: Windows 10
Others:
The text was updated successfully, but these errors were encountered: