Build the Vibe platform example as a shared-component studio - #31
Open
MiguelsPizza wants to merge 3 commits into
Open
Build the Vibe platform example as a shared-component studio#31MiguelsPizza wants to merge 3 commits into
MiguelsPizza wants to merge 3 commits into
Conversation
Replace the hand-built DOM shell with React and the MCP-B design system so the example exercises the same component stack as consumers. Keep the browser-hosted actor, editor, preview, export, and reload behavior covered through the real example E2E path, and type the namespace test through the public Durable Object contract.
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.
Why
The browser-hosted Vibe platform example had a bespoke DOM shell even though consumers use the shared MCP-B component system. Keeping the example on the same component stack makes it a more representative integration boundary without changing runtime behavior.
What changed
The component pins follow the current WebMCP design-system release: https://github.com/WebMCP-org/design-system/releases/tag/%40mcp-b%2Freact-components%400.46.3
Verification