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

Unable to install into Angular 11 project #6

Closed
mindscratch opened this issue Mar 9, 2021 · 4 comments
Closed

Unable to install into Angular 11 project #6

mindscratch opened this issue Mar 9, 2021 · 4 comments

Comments

@mindscratch
Copy link

mindscratch commented Mar 9, 2021

While trying to install into an Angular 11 project using Node 15.4.0 and NPM 7.0.15, it fails:

> npm install zingchart-angular
...
npm ERR! Found: @angular/common@11.0.9
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"~11.0.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^8.2.14" from zingchart-angular@1.0.0
npm ERR! node_modules/zingchart-angular
npm ERR!   zingchart-angular@"*" 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

I was able to reproduce this using a brand new Angular 11 project using Node 15.4.0 and NPM 7.0.15:

> ng new zing-test
> cd zing-test
> npm install zingchart
> npm install zingchart-angular # this is where it fails
@dannyjuergens
Copy link
Contributor

Need to use npm install zingchart-angular --legacy-peer-deps. Updating docs.

@stuurman
Copy link

stuurman commented Mar 26, 2021

This seems to be a workaround not a fix.
Also see the error message of npm (version 7.7.4):
Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

When is the library going to be upgraded to just support angular 11 (soon 12 is already coming) and this one is still fixed to Angular 8?

@zingsoftadmin is there a timeline when it will be at least angular 11 compatible?

@angeltg83
Copy link

hey,
please!!
I need help!!
err-chart

@dannyjuergens
Copy link
Contributor

@angeltg83 This appears to be a network problem, please reference this thread: npm/npm#6820

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

No branches or pull requests

4 participants