Quickly set up Component Explorer with Vite and AI agent integration.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "setup-component-explorer-light" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/vscode-team-kit/main/component-explorer/skills/setup-component-explorer-light/SKILL.md 2. Save it as ~/.claude/skills/setup-component-explorer-light/SKILL.md 3. Reload skills and tell me it's ready
Set up the lightweight version of Component Explorer for my frontend project, install the required dependencies, and add the Vite plugin. Please provide the full commands and file changes.
Provides install commands, setup steps, and example project file changes.
Add an MCP server to my existing Component Explorer setup for AI agent integration, and explain how to start it and verify the connection.
Provides MCP configuration steps, startup commands, and connection verification guidance.
I ran into errors while installing Component Explorer and the Vite plugin. Give me a troubleshooting checklist with likely fixes.
Provides a step-by-step checklist covering dependencies, config, version compatibility, and startup issues.
Minimal setup: install packages and wire the Vite plugin so fixtures are served at ___explorer. For the full setup (CLI daemon, VS Code tasks & launch config), use the setup-component-explorer-full skill.
npm install @vscode/component-explorer @vscode/component-explorer-vite-plugin
Use the project's package manager (npm, pnpm, yarn). For workspace monorepos, install into the package that owns the Vite config.
Add componentExplorer() to vite.config.ts:
import { componentExplorer } from '@vscode/component-explorer-vite-plugin';
export default defineConfig({
plugins: [
// ... existing plugins (react, tailwind, etc.)
componentExplorer(),
],
});
| Option | Default | Description |
|---|---|---|
include | './src/**/*.fixture.{ts,tsx}' | Glob pattern for fixture files |
route | '/___explorer' | URL path for the explorer UI |
build | 'app-only' | Build mode: 'app-only', 'all', or 'explorer-only' |
outFile | '___explorer.html' | Output filename for built explorer |
logLevel | 'info' | 'silent', 'info', 'verbose', 'warn', 'error' |
For projects where fixtures live outside ./src, set include explicitly:
componentExplorer({
include: './test/**/*.fixture.{ts,tsx,js,jsx}',
}),
npx vite, pnpm dev).simpleBrowser.show with url: http://localhost:5173/___explorer
Important: Before writing any fixtures, read the use-component-explorer skill. It covers fixture patterns, project-specific wrappers, and best practices that are essential for correct usage.
To enable AI agents (Copilot) to take screenshots, compare fixtures, and interact with components, add the MCP server.
npm install @vscode/component-explorer-cli
component-explorer.jsonCreate component-explorer.json next to the Vite config (or at the project root). This points the CLI at the running Vite dev server:
{
"$schema": "node_modules/@vscode/component-explorer-cli/dist/component-explorer-config.schema.json",
"sessions": [{ "name": "current" }],
"server": {
"type": "http",
"url": "http://localhost:5173"
}
}
Adjust the url if the dev server uses a different port.
.vscode/mcp.jsonCreate or update .vscode/mcp.json to register the MCP server:
{
"servers": {
"component-explorer": {
"type": "stdio",
"command": "npx",
"args": [
"component-explorer",
"mcp",
"-p",
"./component-explorer.json"
]
}
}
}
Adjust the -p path if component-explorer.json is not at the workspace root.
Analyze VS Code rolling build health and identify breaking commit ranges.
Dismiss specific GitHub notifications to keep your inbox clean and focused.
Manage subscription status for GitHub notification threads and reduce noise.
Mark all GitHub notifications as read to quickly clear your inbox.
Store, organize, and retrieve inbox content for faster follow-up work.
Fetch and review GitHub notifications quickly using the gh CLI.
Set up Component Explorer with CLI, MCP, and VS Code tooling.
Scan React and Vue projects to expose component metadata for AI coding agents.
Provides MCP access to browsers for debugging console, storage, performance, and component trees.
Query Svelte project component graphs, unused components, and route dependencies.
Control Chrome DevTools with AI for debugging, screenshots, and script execution.
Lets AI agents run Python, execute scripts, and install pip packages locally.