Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error, when using strictTemplates in Angular 9.
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 (@ngx-translate/core) which declares TranslateModule 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.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:25
Top Results From Across the Web
strictTemplates in Angular 9 generates error #3628 - GitHub
Enabling the new strictTemplates flag in Angular 9's compiler options generates the following build error:
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 >Template type checking - Angular
With strict mode, you might encounter template errors that didn't arise in either of the previous modes. These errors often represent genuine type...
Read more >Angular 9, strict templates, incompatible types build errors
I am getting the same error when I use strict mode in an angular project. In the mean time, for a workaround: if...
Read more >Error in ngModel when strictTemplates is true in angular 12
I have one project in Angular 12 which is giving a problem after the notation strictTemplates. In my component I have this property:...
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
Hi guys, this fixed the problem for me: npm cache verify
Remove the node modules rm -rf node_modules
And npm install again and it works properly.
@Shadab-97-eng see my updated code. This works fine for me now.