feat(examples): expose Bridge export-app from Nuxt remote - #21
Open
tonoizer wants to merge 4 commits into
Open
Conversation
Add a minimal createBridgeComponent export on the remote and a host catch-all under /bridge so the same app-level remote can be loaded alongside existing component federation. Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid host manifest discovery registering the Bridge factory as RemoteExportApp by exposing ./bridge/export-app instead of ./export-app. Co-authored-by: Cursor <cursoragent@cursor.com>
tonoizer
marked this pull request as ready for review
August 11, 2026 18:19
This was referenced Aug 11, 2026
Point hosts at pathMatch catch-alls for current bridge-vue3 and link core#4984 for the upcoming explicit basename API. Co-authored-by: Cursor <cursoragent@cursor.com>
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
./bridge/export-appviacreateBridgeComponent(small vue-router app underapp/bridge/)./bridge/:pathMatch(.*)*withcreateRemoteAppComponent(ClientOnly island).RemoteExportApp./unchanged.Plan (Bridge meta-framework remotes)
Same Bridge remote should load in Nuxt and React/Next without a second build. Split across:
bridge-vue3basename (explicit + Nuxt catch-alls)/bridgeSSR: module-federation/core#4869 (separate). This PR is CSR Bridge only.
Testing
pnpm --filter @module-federation/nuxt buildpnpm --filter nuxt-remote typecheckpnpm --filter nuxt-host typecheckRisks
NuxtPage); existing e2e that hit/should still see component cards.bridge-vue3peersvue-router@4while Nuxt 4 uses v5 — runtime APIs used here overlap; watch peer warnings.:pathMatch(.*)*catch-all; explicitbasenamelands with core#4984.Non-goals