Navigation and nested page-router-outlet with lazy loaded children

リンク先の ns-login-tab-navigation-ng13 の例から始め、ネストされた page-router-outlet の構成を適用して、プレイヤーとチームの詳細を遅延ロードします。ルーターイベントを追跡しながら @nativescript/angular 13.0.1 と 13.0.2 の動作を比較します。完了条件は、詳細への移動と戻る操作を繰り返しても、タブ間で引き続き正常に動作することです。

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

• CLI: 8.1.5
• Cross-platform modules: 8.1.5
• Android Runtime: 8.1.0
• iOS Runtime: 8.1.1
• Plugin(s): "@nativescript-community/ui-material-bottom-navigation": "~6.2.13"
• NativeScript-Angular: 13.0.2
• Angular: 13.1.1

Describe the bug

Navigation for a page-router-outlet is not working anymore after navigating back from details view.

I have a navigation setup with nested page-router-outlets, much like this example, except the children (player details and team details) are also lazy loaded modules with their own routes.

After starting the app, and the tabs are loaded with their lazy loaded module, I can navigate to the details view and back. However, when I try to navigate to the details view again, there's no response. I have enabled tracing on the router, and there are no events fired when navigating back. Also no events are fired on new navigation attempts.

If I navigate to another tab, I can repeat the process. Then that will be "stuck" as well.

To Reproduce
Use the example from the link above and lazy load the details components.

Expected behavior
Navigation should keep working regardless of lazy loaded children.

Sample project

Additional context

This was working in @nativescript/angular 13.0.1, but then with issues like #49 and #53