-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Error when building with AOT enabled when using Angular #3620
Comments
Not a proper solution, but by rolling back to Altho, you may be welcomed by a new error regarding |
@HiDeoo Thank you for your help. I've solved my problem by going back to |
@jeremyputeaux, @HiDeoo - I think this error is caused by: tsconfig:
Disabling the 'fullTemplateTypeCheck' should move you forward (although ultimately this should not be necessary). I believe I know what the underlying issue is and will continue digging into it. |
@haverchuck Yes that is correct. Disabling |
Great to find this tread and the solution provided by @haverchuck. I am integrated Amazon Cognito into a JHipster based Angular app. Got the plumbing in place and then hit this issue when I tried to deploy for production. Found this discussion and, 10 minutes later, I'm in business! Just disabled fullTemplateTypeCheck in tsconfig-aot.json in my case and got past the issue. |
…d due to aws amplify package issue. See aws-amplify/amplify-js#3620
I had this problem as well, and it looks like putting "fullTemplateTypeCheck" to false in tsconfig.json also made the errors go away. Is it ok to leave it like this for production? And any further info as to what the cause of this could be? |
Disabling fullTemplateTypeCheck is an awful solution. The point of Angular + Typescript is to prevent type errors. Disabling type checking project wide because 1 lib can't fix their problems is not the right solution. |
So the reason is that a Is anyone working on a PR? |
…or template checking aws-amplify#3620
@hfahlbusch ah haven't seen that. Maybe we can |
Did you |
I agree with this but can't see a workaround until the PR is merged. Did anyone come across any other solutions other than disabling |
Dropping AWS Datastore should help |
The new Amplify Angular UI Authenticator support Angular 9 and AOT. I am going to close this issue now. If you are having trouble using the new UI component library or are trying to use components other than the Authenticator, please open a new issue with the details and reproduction steps. Here is a link to the new UI documentation: |
@jordanranz Does that mean Amplify supports Angular 9 as well, or just Amplify Angular UI? This page still says Angular 9 is not supported. |
@jordanranz surely you could approve this pr #4883 rather than leaving the code broken? |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
I'm running a basic ng build --prod and I'm getting the following error:
I reported the problem on the Angular side and they answered
You can see it here: angular/angular-cli#15035
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I'm expecting the build to work.
Desktop (please complete the following information):
Additional context
I'm using Window 10 and the WSL.
Sample code
https://github.com/jeremyputeaux/angular8-amplify-aot-build-problem
You just need: npm i and ng build --prod
The text was updated successfully, but these errors were encountered: