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

Compatibility with Angular 11 #544

Open
2 of 17 tasks
xyassini opened this issue May 9, 2021 · 0 comments
Open
2 of 17 tasks

Compatibility with Angular 11 #544

xyassini opened this issue May 9, 2021 · 0 comments

Comments

@xyassini
Copy link

xyassini commented May 9, 2021

I'm submitting a...

  • Regression (a behavior that used to work and stopped working in a new release)
  • Bug report
  • Performance issue
  • Feature request
  • Documentation issue or request
  • Other... Please describe: Basically the same as Compatibility With Angular 9 #517

Current behavior

npm i with 9.0.0-beta.0 fails with dependency errors:

npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"~11.2.13" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.0.0" from [email protected]
npm ERR! node_modules/angular-token
npm ERR!   angular-token@"9.0.0-beta.0" from the root project

Expected behavior

angular-token should be installable with Angular 11

What is the motivation / use case for changing the behavior?

Created a new application with Angular 11

Environment

Angular-Token version: 9.0.0-beta.0
Angular version: 11.2.13

Bundler

  • Angular CLI (Webpack)
  • Webpack
  • SystemJS

Browser:

  • Chrome (desktop) version XX
  • Chrome (Android) version XX
  • Chrome (iOS) version XX
  • Firefox version XX
  • Safari (desktop) version XX
  • Safari (iOS) version XX
  • IE version XX
  • Edge version XX

Others:
Works when installing with npm i --force, though it's not an optimal solution of course.
I didn't test the actual functionality yet, but will report about that in a few days.

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

1 participant