Compatibility with Angular 11

[xyassini]

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
• [x] Other... Please describe: Basically the same as https://github.com/neroniaky/angular-token/issues/517

Current behavior

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

npm ERR! While resolving: frontend@0.0.0
npm ERR! Found: @angular/common@11.2.13
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 angular-token@9.0.0-beta.0
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

• [x] 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.