search

articodeltd / angular-cesium

JavaScript library for creating map based web apps using Cesium and Angular
https://github.com/articodeltd/angular-cesium/settings/pages
MIT License
178 stars 93 forks source link

Angular 13 #432

Open sleagle opened 2 years ago

sleagle commented 2 years ago

When I try to install angular-cesium I am getting the following error. I am currently using Angular 13. Would like to know if this application supports Angular 13.

`code ERESOLVE ERESOLVE unable to resolve dependency tree

While resolving: angular-cesium-tut@0.0.0 Found: @angular/common@13.3.11 node_modules/@angular/common @angular/common@"~13.3.0" from the root project

Could not resolve dependency: peer @angular/common@"^9.0.1 || ^10.0.0 || ^11.0.0" from angular-cesium@0.0.73 node_modules/angular-cesium angular-cesium@"*" from the root project

Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.`

Thanks

Bella303 commented 2 years ago

I have the same issue when trying to install angular-cesium. I am also using Angular 13. Will there be a new release soon that can support Angular 13?

Per the npm CLI config docs: "Use of legacy-peer-deps is not recommended, as it will not enforce the peerDependencies contract that meta-dependencies may rely on."

Thanks

Bella303 commented 2 years ago

When I try to install angular-cesium I am getting the following error. I am currently using Angular 13. Would like to know if this application supports Angular 13.

`code ERESOLVE ERESOLVE unable to resolve dependency tree

While resolving: angular-cesium-tut@0.0.0 Found: @angular/common@13.3.11 node_modules/@angular/common @angular/common@"~13.3.0" from the root project

Could not resolve dependency: peer @angular/common@"^9.0.1 || ^10.0.0 || ^11.0.0" from angular-cesium@0.0.73 node_modules/angular-cesium angular-cesium@"*" from the root project

Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.`

Thanks

Issue #419 makes it sound like there will not be a resolution anytime soon as they are looking for maintainers.

arye97 commented 1 year ago

You can get around this by running npm i --legacy-peer-deps, which forces npm packages to resolve. This isn't a great solve, but you can get it to work until angular-cesium is upgraded!