-
Notifications
You must be signed in to change notification settings - Fork 115
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
4.1.0
has no longer support Angular 11
#134
Comments
I'm using the package in an angular 12 project as well, and it has no issues at all. Have you tried deleting your node_modules folder and installing them all again? You could also try this in combination with deleting the lock file. It is possible there is something wrong in the dependencies. |
@venraij thanks you for response. Yes, I deleted node_modules folder and install again and same error, we found the problem in CI pipeline, where install is in cleaned up folder. So I downgrade to |
What seems strange to me is that it's trying to go into @angular/core/core, that path does not exist. |
I understand, checking again. |
@venraij my apologizes, the angular version in my project is We have in roadmap upgrade to angular 12 so by the moments we can use |
4.1.0
has no longer support Angular 124.1.0
has no longer support Angular 11
The 4.1.0 update doesn't involve big changes though besides the angular 13 upgrade. So there is not much reason to put a lot of time into it. |
@venraij did you install |
Yes, this is the testing project within the repo. I downgraded it to ng 11 for testing. It seems to work fine. |
ok, i will check and report here. Thanks for you help 😄 |
@venraij the issue apparently is related with npm registry, I provide an StackBlitz repro link: https://stackblitz.com/edit/angular-ivy-grjm68?file=src/app/app.component.ts |
I've created a fix #136 |
thanks you @venraij !! i will check when new version is available. |
Hi! Today I upgrade
ngx-mat-intl-tel-input
from4.0.0
to4.1.0
and the application not compile because a lot of errors.The text was updated successfully, but these errors were encountered: