Currently, this modules only handles entity routes. When Drupal resolves the path to a non-entity route, an error is returned. Non entity routes may be defined in the frontend e.g. the Next server, or they may exist as Drupal routes e.g. Views in applications that have multiple frontends - some Drupal frontends and some decoupled frontends, possibly transitioning from Drupal frontends to fully decoupled.
In any case, even when non-entity routes are defined in the frontend e.g. Next server, content editors commonly need to create redirects from, say, a a product that was unpublished to a specific catalog page. For example, `/product/1234` to `/search?category=new-tshirt-collection`.
To have these redirects handled in the frontend would not be ideal. It creates two systems from entering redirects, potentially no UI in the frontend, and in some cases it might bypass the access control checks that might be needed.
In the Drupal backend, create a redirect, for example, to the login page, or to a route provided by Views that may also have a corresponding implementation in the frontend in multi-domain/multi-frontend.
Existing code makes it difficult to alter the behavior without patching the module. I think that we need to provide a pluggable way for third-party code to handle non-entity routes. This module could potentially add automatic support for some standard Drupal routes e.g. login, Views etc.
Determine approach first.
Active
2.0
Code
I think if we limit this to redirects this is quite easy to support and inline with the support for external redirects too... see 📌 Support redirects to non-content entity pages for example a view Active - I think this issue is a duplicate of that one.