Add getReactSource to extract React component source location
- Add bippy library for React fiber introspection - Create build-bippy.ts and build-selector-generator.ts using Bun.build - Use CDP Runtime.evaluate instead of addScriptTag to bypass CSP - Add getReactSource utility function exposed in MCP VMContext - Works on local React dev servers with JSX transform (not production builds)
This commit is contained in:
@@ -1,5 +1,18 @@
|
||||
# Changelog
|
||||
|
||||
## 0.0.28
|
||||
|
||||
### Patch Changes
|
||||
|
||||
- **Added `getReactSource` utility**: Extract React component source location (file, line, column) from DOM elements
|
||||
- Uses bippy library for React fiber introspection
|
||||
- Returns `{ fileName, lineNumber, columnNumber, componentName }` or `null`
|
||||
- Only works on local dev servers (Vite, Next.js, CRA) with JSX transform in development mode
|
||||
- **CSP bypass for script injection**: Changed `getLocatorStringForElement` and `getReactSource` to use CDP `Runtime.evaluate` instead of `addScriptTag`
|
||||
- Scripts now work on pages with strict Content Security Policy
|
||||
- **Switched to Bun.build**: Replaced esbuild and esm.sh downloads with Bun.build for bundling selector-generator and bippy
|
||||
- New `build-selector-generator.ts` and `build-bippy.ts` scripts
|
||||
|
||||
## 0.0.27
|
||||
|
||||
### Patch Changes
|
||||
|
||||
Reference in New Issue
Block a user