@mcpc-tech/unplugin-dev-inspector-mcp 0.1.2 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,8 +1,4 @@
1
- <p align="center">
2
- <img src="./assets/logo.svg" alt="DevInspector Logo" width="50" height="50" />
3
- </p>
4
-
5
- # @mcpc-tech/unplugin-dev-inspector-mcp
1
+ # dev-inspector-mcp
6
2
 
7
3
  [![npm version](https://img.shields.io/npm/v/@mcpc-tech/unplugin-dev-inspector-mcp.svg)](https://www.npmjs.com/package/@mcpc-tech/unplugin-dev-inspector-mcp)
8
4
  [![npm downloads](https://img.shields.io/npm/dm/@mcpc-tech/unplugin-dev-inspector-mcp.svg)](https://www.npmjs.com/package/@mcpc-tech/unplugin-dev-inspector-mcp)
@@ -46,17 +42,22 @@ Works with any MCP-compatible AI client. Supports ACP agents: **Claude Code**, *
46
42
 
47
43
  ## Key Features
48
44
 
49
- ### 🎯 Visual Context
45
+ ### 🎯 Visual Context & Region Selection
46
+
47
+ Click any element to inspect it, or **drag to select a region**. AI gets the full context: source code location, computed styles, component hierarchy, IDs, classes, text content, and **automatically captures screenshots** for pixel-perfect visual understanding.
48
+
50
49
 
51
- Click any element to instantly send its source code location, computed styles, and DOM hierarchy to AI. No more explaining "it's the blue button in the header".
50
+ ### 🛠️ Universal DevTools Access
52
51
 
53
- ### 🛠️ Full DevTools Access
52
+ AI can access Network and Console logs from **any browser** (via client-side interception) or full Chrome DevTools (via chrome devtools mcp). It sees what you see, regardless of your environment.
54
53
 
55
- AI can access Chrome DevTools to analyze network requests, console logs, and performance metrics. It sees what you see.
54
+ ### Smart Select
55
+
56
+ Let AI do the heavy lifting. "Smart Select" automatically analyzes recent console errors and failed network requests to construct the perfect context for your debugging session.
56
57
 
57
58
  ### 🤖 Multi-Agent Workflow
58
59
 
59
- Switch between agents (Claude Code, Goose) and track their debugging progress visually with step-by-step status updates.
60
+ Switch between agents (Claude Code, Codex, Gemini, Opencode...) and track their debugging progress visually with a **floating status bar**.
60
61
 
61
62
  ## Quick Start
62
63
 
@@ -266,6 +267,31 @@ export default function RootLayout({ children }) {
266
267
  - **Webpack mode:** `next dev` (uses webpack configuration)
267
268
  - **Turbopack mode:** `next dev --turbopack` (uses turbopack configuration, Next.js 16+ default)
268
269
 
270
+
271
+ ### React Router v7+
272
+
273
+ Since React Router handles HTML generation via its own SSR/SPA mechanism, it bypasses the standard Vite HTML transformation hooks. You need to manually import the virtual module in your entry file.
274
+
275
+ ```typescript
276
+ // app/root.tsx or app/entry.client.tsx
277
+ import 'virtual:dev-inspector-mcp';
278
+ ```
279
+
280
+ And ensure your `vite.config.ts` has the plugin:
281
+
282
+ ```typescript
283
+ // vite.config.ts
284
+ import { reactRouter } from "@react-router/dev/vite";
285
+ import DevInspector from '@mcpc-tech/unplugin-dev-inspector-mcp';
286
+
287
+ export default defineConfig({
288
+ plugins: [
289
+ DevInspector.vite({ enabled: true }),
290
+ reactRouter(),
291
+ ],
292
+ });
293
+ ```
294
+
269
295
  ## Framework Support
270
296
 
271
297
  ### ✅ Fully Supported
@@ -281,6 +307,8 @@ export default function RootLayout({ children }) {
281
307
 
282
308
  - **Angular** - Support coming soon
283
309
 
310
+
311
+
284
312
  ## Configuration
285
313
 
286
314
  ### Auto-Update MCP Config