Wildcard route (**) does not catch "Named router-outlet not found" · Issue #40845 · angular/angular · GitHub
![Angular Tutorial - Routing and Navigation | Nested Route in Angular | Setting up Redirect in Angular | Navigation, App development companies, App development Angular Tutorial - Routing and Navigation | Nested Route in Angular | Setting up Redirect in Angular | Navigation, App development companies, App development](https://i.pinimg.com/736x/fd/09/20/fd092044d77b08c0a56a7c962d48a74a.jpg)
Angular Tutorial - Routing and Navigation | Nested Route in Angular | Setting up Redirect in Angular | Navigation, App development companies, App development
App Shell not generated when wildcard route (not found page) is present in app · Issue #8929 · angular/angular-cli · GitHub
![angularjs - How to filter Azure ApplicationInsights client-side browser routes by wildcard routes - Stack Overflow angularjs - How to filter Azure ApplicationInsights client-side browser routes by wildcard routes - Stack Overflow](https://i.stack.imgur.com/O3Evb.png)