feat: add verified Rsbuild federation monorepo - #191
Draft
zackarychapple wants to merge 4 commits into
Draft
Conversation
Merged
10 tasks
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.
What changed
rsbuild-mf-monorepo-*Zephyr application identities while preserving the local Module Federation aliasesheaderandherothrough explicit dependency UID mappingsname@URLstring remotes compatible with the currently released Zephyr1.2.xrewrite pathtemplates.jsonand the examples READMEWhy
Executable product fixtures belong in
zephyr-examples. The documentation PR should consume and link to this example rather than own a second application corpus.The broad repository workflow also exposed two released-system integration boundaries. Object-form
externalremotes were serialized into malformed runtime code during Zephyr rewriting, so the canonical fixture uses the released-compatible string form. Generic application names also collided with an existing repository fixture’s deployment validation, so this example now uses stable, unique application UIDs. Both paths are covered by verification and an authenticated live build.Verification
pnpm install --frozen-lockfilepnpm verify:scaffoldpnpm verifypnpm verify:browserZE_FAIL_BUILD=true pnpm run buildwith authenticated live Zephyr deploymentspnpm --dir scripts buildpnpm --filter @zephyr-examples/scripts generate-templatespnpm --filter @zephyr-examples/scripts generate-readmepnpm --filter @zephyr-examples/scripts validate-readmesgit diff --checkLocal verification passed. The local shell used Node 26.4.0 and emitted the expected engine warning; CI pins Node 24 as declared by the example.