feat(angular): use provideRouter for standalone remote apps #18468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
Remote applications based on standalone components generated using
nx g @nx/angular:remote remote-name --standalone
or
nx g @nx/angular:host shell --remotes=remote-name --standalone
use
importProvidersFrom
in theirbootstrap.ts
while an already generated and currently unusedappConfig
withprovideRouter
from newer Router API could be used.It is worth noting that generators for other types of applications were already switched to use the new API in #12012. That also includes generating
host
applications using the command above.Expected Behavior
Generated remote applications with standalone components utilize already generated
appConfig
withprovideRouter
instead ofimportProvidersFrom
in theirbootstrap.ts
files. This way all generators for standalone components applications use the same newer Router API.Related Issue(s)
Fixes #