strictTemplates in Angular 9 generates error
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 (@ng-bootstrap/ng-bootstrap) which declares NgbModule 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.
I am using latest ng-bootstrap.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Template type checking - Angular
When you enable strictTemplates and the TypeScript flag strictNullChecks , typecheck errors might occur for certain situations that might not easily be avoided....
Read more >Angular 9's Best Hidden Feature: Strict Template Checking
Find and report more errors than ever with Angular 9's Ivy compiler, strict template checking.
Read more >eslint Angular Strict Template Checks should show error
We have angularCompilerOptions.strictTemplates: true set for all the applications. The problem is that we have a CI pipeline that checks for ...
Read more >strictTemplates in Angular 9 generates error - Bountysource
Enabling the new strictTemplates flag in Angular 9's compiler options generates the following build error:
Read more >Angular 9, strict templates, incompatible types build errors
After enabling the strictTemplates compiler option in Angular 9 I am seeing a number of build errors with the TreeView.
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 Free
Top 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
I’ve had this error several times during the process of updating recently.
It has gone away each time for me by deleting my ./dist directory, package-lock.json and node_modules directory