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.
Not working with angular 12
See original GitHub issueThe angular-notifier no longer works with angular 12.
Are there any plans on upgrading?
Maybe it is just a simple version bump in the peer dependencies sections, but I am not that familiar with angular.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:7 (1 by maintainers)
Top Results From Across the Web
NG Add on Angular 12 not working · Issue #1471 - GitHub
A workaround is installing earlier version of schematics -the same one the library uses. npm install @schematics/angular@9.1.12.
Read more >Angular Routes are not working in Angular 12 - Stack Overflow
Hi, saw you have AppRoutingModule and RouterModule in app.module.ts. Please remove RouterModule . Expected you will export RouterModule from ...
Read more >Hansontable not working in angular 12 - Questions
I am using angular 12 but Hansontable context and formula not working .
Read more >Lazy-loading feature modules - Angular
By default, NgModules are eagerly loaded. This means that as soon as the application loads, so do all the NgModules, whether they are...
Read more >How To Fix Your Angular App When It's Not Working in IE11
Run your application: ng serve --configuration es5 . I recommend to add a run script in package.json for convenience.
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
request to make it compatible with NG13
as a temporary fix you could use
npm i angular-notifier --forcesince everything seems to be working fine.