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

Can not install with [email protected] #13197

Closed
steve3d opened this issue Jun 14, 2023 · 7 comments · Fixed by #13203
Closed

Can not install with [email protected] #13197

steve3d opened this issue Jun 14, 2023 · 7 comments · Fixed by #13203
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@steve3d
Copy link
Contributor

steve3d commented Jun 14, 2023

Describe the bug

primeng-16.0.0 can not install with [email protected], in package.json the version is set to ~16.0.0 which exclude any 16.x version:

"@angular/core": "~16.0.0",

this will only allow primeng be installed with [email protected] version.

Environment

no matter.

Reproducer

No response

Angular version

16.1.0

PrimeNG version

16.0.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

v18.16.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

should be installed with [email protected]

@steve3d steve3d added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jun 14, 2023
@adri95cadiz
Copy link

Same for me, please review this.

Thanks a lot

@ces6jedi
Copy link

+1

1 similar comment
@igordanilovski
Copy link

+1

@cretara
Copy link

cretara commented Jun 14, 2023

I suggest u to install with
npm i -f

I didn't notice issues in my projects

@igordanilovski
Copy link

Yes, it works with npm i -f but that is not a solution, they need to fix this.

@gottaloveit
Copy link

It's not working for me with Angular 16.0.0

Below is npm output and my package.json and package-lock.json

PS C:\Users\gotta\Desktop\New folder\Streaming> npm i primeng
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"16.1.1" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     peerOptional @angular/animations@"16.1.1" from @angular/[email protected]
npm ERR!     node_modules/@angular/platform-browser
npm ERR!       peer @angular/platform-browser@"16.1.1" from @angular/[email protected]
npm ERR!       node_modules/@angular/forms
npm ERR!         @angular/forms@"^16.0.0" from the root project
npm ERR!       3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
npm ERR!     @angular/animations@"^16.0.0" from the root project
npm ERR!   peer @angular/core@"16.1.1" from @angular/[email protected]
npm ERR!   node_modules/@angular/common
npm ERR!     peer @angular/common@"16.1.1" from @angular/[email protected]
npm ERR!     node_modules/@angular/forms
npm ERR!       @angular/forms@"^16.0.0" from the root project
npm ERR!     peer @angular/common@"16.1.1" from @angular/[email protected]
npm ERR!     node_modules/@angular/platform-browser
npm ERR!       peer @angular/platform-browser@"16.1.1" from @angular/[email protected]
npm ERR!       node_modules/@angular/forms
npm ERR!         @angular/forms@"^16.0.0" from the root project
npm ERR!       3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
npm ERR!     3 more (@angular/platform-browser-dynamic, @angular/router, the root project)
npm ERR!   6 more (@angular/compiler, @angular/forms, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! primeng@"*" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"~16.0.0" from [email protected]
npm ERR!   node_modules/primeng
npm ERR!     primeng@"*" 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!
npm ERR! For a full report see:
npm ERR! C:\Users\gotta\AppData\Local\npm-cache\_logs\2023-06-14T23_27_42_553Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: C:\Users\gotta\AppData\Local\npm-cache\_logs\2023-06-14T23_27_42_553Z-debug-0.log

package.json.txt
package-lock.json.txt

@cretara
Copy link

cretara commented Jun 15, 2023

Yes, it works with npm i -f but that is not a solution, they need to fix this.

Sure, it's true, that's an issue that must be solved.

Sami issue happens with Angular 16.1.1 released yesterday

@cetincakiroglu cetincakiroglu added this to the 16.0.1 milestone Jun 16, 2023
@cetincakiroglu cetincakiroglu added Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Jun 16, 2023
@cetincakiroglu cetincakiroglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add labels Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants