Angular 15 - router.events are empty with nested router outlets on page refresh about angular HOT 1 CLOSED

This is due to the following breaking change, from the 15.0 release notes:

Previously, the RouterOutlet would immediately instantiate the component being activated during navigation. Now the component is not instantiated until the change detection runs. This could affect tests which do not trigger change detection after a router navigation. In rarer cases, this can affect production code that relies on the exact timing of component availability.

In other words, the component can't observe its own navigation events.

The navigation from orders to customers shows the same behavior for the first navigation to customers. Subsequent navigations work because of the stale subscription from the prior instance that was never unsubsribed.

Per the breaking change this is working as expected.

from angular.