Add standalone dev harness for UI iteration#11
Draft
maxcold wants to merge 2 commits into
Draft
Conversation
…ktop Vite-based gallery that mocks @modelcontextprotocol/ext-apps via resolve.alias, rendering all 6 views with configurable mock data states and theme switching. Run with `npm run standalone` at localhost:3456.
- Update mock data shape for check-existing-sample-data to match App expectations (totalDocs, totalAlerts, existingRules, byScenario) - Fix race condition: connect() now awaits mock data module loading before resolving, preventing callServerTool from hitting an empty registry
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
npm run standalone) for visual UI iteration without Claude Desktop@modelcontextprotocol/ext-appsvia Viteresolve.alias— zero changes to view source codeMoved from elastic/wip-example-mcp-app-security#8
Test plan
npm run standalone, verify harness loads at localhost:3456npm run buildto confirm no regressions in production build