-
Notifications
You must be signed in to change notification settings - Fork 485
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
Angular 11 SUPPORT #697
Comments
I am currently using angular v11 and I am not facing any issues.... |
I use Angular 11 and I have problems, the configuration that is added to the JwtModule does not react, it does nothing. In Angular 10 I did not have this problem, I created a project from scratch with angular 11 and it did not work either, so the library only works until version 10, I hope you can review this problem |
in angular 1 1 got: node_modules/angular2-jwt/angular2-jwt.d.ts:1:77 - error TS2307: Cannot find module '@angular/http' or its corresponding type declarations. |
I'm using angular 12 without issue |
confirmed with angular 11 without issue. |
We've used this package with Angular 10 and 13 without issue. Have you made sure to install the right version? If you use version 4.2.0 it should work. |
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! 🙇♂️ |
Hi, it's still an issue for us, we are waiting for the Ivy support using the partial compilation mode. |
@edbzn sre you using |
@Rlcolli4 @auth0/angular-jwt@5.0.2 was published with ViewEngine which means ngcc needs to be run by the consumer to bring Ivy compatibility, here is the log of the webpack plugin processing angular-jwt using ngcc:
If we want to get rid of ngcc one day we have to encourage library authors to publish using the partial compilation mode. |
Interesting, we haven't seen that when we run locally or when we send a build out. Maybe we have missed it. I will double check our outputs, but currently we do not have any issue running that in our set up. |
Closing this in favor of #712 |
Hi, when can we expect angular 11 support??
The text was updated successfully, but these errors were encountered: