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.
Dependency on @angular/router breaks compatibility with Ionic
See original GitHub issueWe’re currently trying to use angular-application-insights across our various Angular applications, one of which is built in Ionic. Given the current version of Ionic (v.3) does not use @angular/router, we are getting the same error mentioned in Issue #25 Unhandled Promise rejection: No provider for Router!, which is due to the hard dependency on Angular Router inside AppInsightsService.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
feat: support Angular 14 #25353 - ionic-team/ionic-framework
In Angular 14, there is a breaking change that removes the deprecated ComponentFactoryResolver , specifically from router outlets.
Read more >Resolve version conflicts when adding Angular Material to an ...
I am working on an Ionic angular project.
Read more >App Migration Guide: Documentation to Migrate Ionic 4.x to 5.x
The Ionic Migration Guide provides documentation for how to migrate an app from 4.x to 5.x. Read to learn more about what updates...
Read more >Update Angular to v15
This topic provides information about updating your Angular applications to Angular version 15. For a summary of this information and the step-by-step ...
Read more >Deprecated APIs and features - Angular
@angular/router, resolver field of the OutletContext class, v14, v16. @angular/service-worker, SwUpdate# ... No source code should depend on this API.
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
Yeah I think we might need to omit it entirely and warn people that they need to add that code themselves if they want it to handle those events, let me test a few things out.
Fixed with the latest version 5.0.4 @GFoley83 We’re grabbing the Router via the Injector now, so it shouldn’t have any issues now! Sorry about the delay there.
Closing out but please open up if it still didn’t fix it!