We have integrated a single-spa microfrontend architecture to host multiple Angular applications. Each Angular project has been configured with a custom RouteReuseStrategy to support Back/Forward Cache (bfcache) functionality.
The reuse strategy works as expected within individual Angular applications. However, when navigating from one Angular application to another through single-spa, the RouteReuseStrategy does not behave correctly and the state is not preserved.
Steps to Reproduce:
- Navigate within an Angular app — Back/Forward Cache works as expected.
- Navigate from App A to App B (both hosted via single-spa).
- Attempt to go back — the state is not restored as intended.
Expected Behavior:
State should be preserved across navigation between different Angular apps using the configured RouteReuseStrategy.
We have integrated a single-spa microfrontend architecture to host multiple Angular applications. Each Angular project has been configured with a custom RouteReuseStrategy to support Back/Forward Cache (bfcache) functionality.
The reuse strategy works as expected within individual Angular applications. However, when navigating from one Angular application to another through single-spa, the RouteReuseStrategy does not behave correctly and the state is not preserved.
Steps to Reproduce:
Expected Behavior:
State should be preserved across navigation between different Angular apps using the configured RouteReuseStrategy.