Routing stops working with no errors being shown about angular

[garrettld]

You're providing the Router class in a couple components. The Router should only be provided once, in the root, with provideRouter.

Re-providing it causes the child Router to be destroyed when the view that provides it is destroyed, which completes the navigation transitions observable, so the root router never sees any additional navigation events. Your app should work normally if you remove Router from your component providers arrays.

It would be nice if there was a runtime warning when multiple Router instances were detected.

[jamesmcging]

You're providing the Router class in a couple components. The Router should only be provided once, in the root, with provideRouter.

Re-providing it causes the child Router to be destroyed when the view that provides it is destroyed, which completes the navigation transitions observable, so the root router never sees any additional navigation events. Your app should work normally if you remove Router from your component providers arrays.

It would be nice if there was a runtime warning when multiple Router instances were detected.

@garrettld, you're a star, I've just spent 3 days trying to work out why exactly this was happening to me and you answered in your first line.

[BnSmth]

Thank you so much @garrettld, that's resolved the issue. Totally agree that some sort of warning should be raised if multiple instances are detected (at least when running in dev mode). Thanks again, this was an incredibly frustrating issue that was really bumming me out!