strictTemplates, Angular 9: compability with Ivy
See original GitHub issueEnabling the new strictTemplates flag in Angular 9’s compiler options generates the following build error:
This likely means that the library (@angular/platform-browser/animations) which declares BrowserAnimationsModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.
Error appears for multiple components:
- @angular/platform-browser/animations
- @angular/router
- @angular/material/sort
- @angular/material/paginator
- @angular/material/datepicker
- @angular/material/icon
- @angular/material/core
- @angular/forms
And maybe in some other. But these ones i am using in my project.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:35
- Comments:56 (18 by maintainers)
Top Results From Across the Web
Angular 9's Best Hidden Feature: Strict Template Checking
When strictTemplates is true, Angular 9 and the Ivy compiler verify that hero is a valid model of type Hero , and that...
Read more >All Perks, No Hassle: An Angular 9 Tutorial - Toptal
Angular 9 and Angular Ivy: Better Development, Better Apps, and Better Compatibility. In this Angular 9 tutorial, we've covered building a basic form,...
Read more >Version 9 of Angular Now Available — Project Ivy has arrived!
Version 9 moves all applications to use the Ivy compiler and ... strictTemplates — Activating this flag will apply the strictest Type System ......
Read more >All About Angular Engine Ivy in 5 mins
IVY is a rendering architecture that was first introduced with Version 8. ... View Engine-compatible libraries for Angular version 9.
Read more >A look at major features in the Angular Ivy version 9 release
The Angular compatibility compiler will upgrade View Engine-compatible libraries to Ivy when installed in an Angular Ivy application project ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Dunno if it helps, but so far I only appear to get the cited errors when I first add an import for a given material module while
ng serve
is running;ng build
&ng build --prod
aren’t throwing any errors for me, and if I stop & restartng serve
it compiles & runs w/o any further issue.I will add that I’m working with a brand new project, so there’s not a lot else going on, yet.
If this can help anybody, I got the same error with MatRipple and I (wrongly) thought that it was linked to this issue, but after disabling Ivy the error message changed to :
Then I realised that I was trying to import MatRipple instead of MatRippleModule. The mistake is clearly on my side, but I think the error message in Ivy was not very helpful.