Upgrade angular to v11

[celian-garcia]

Hi, thanks for this library, I'm planning to update progressively until Angular v13, with one commit by Angular version (one for v11, on for v12, one for v13). I plan to move linter to eslint in the Angular v12 commit.
Please tell me if you agree with these changes and thus if I can continue or not.

The objective is at the end to get rid of the warning in v13 #712

Cheers!

Changes

• Upgraded Angular to v11 using ng update

References

• Probably fixes this Angular 11 SUPPORT #697, even though I think it works perfectly with Angular 11 as we ran our frontend on Angular 11 without issue for monthes.

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines in the CONTRIBUTING documentation have been run/followed
• All relevant assets have been compiled as directed in the CONTRIBUTING documentation, if applicable

[PedroS5499]

why this taking so long?

[celian-garcia]

why this taking so long?

I agree it's a bit long, I'm wondering if it's still maintained. To be honest I'm considering making a fork.

Hello @Sambego, sorry I mention you as you are the last commiter. I'd like to remind you the fact that Angular 10 is not anymore an LTS, and so doesn't receive any security updates, according to the Angular Support Policy documentation.

If Auth0 still uses this project, it should be updated for sure!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

[PedroS5499]

No no, no stale

[celian-garcia]

@PedroS5499 did you find a substitute ? I don't want to maintain a fork so I will search for another lib or maybe integrate stuff in my code place.

[frederikprijck]

Closing this in favor of #712