dev3000 0.0.169 → 0.0.170

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.
@@ -33,37 +33,38 @@ d3k find-component "nav" # Find React component source
33
33
 
34
34
  ## Browser Interaction
35
35
 
36
- To click elements, navigate, or take screenshots, use `d3k agent-browser --cdp $(d3k cdp-port)`:
36
+ First run `d3k cdp-port` to get the port number, then use it directly in all browser commands:
37
37
 
38
38
  ```bash
39
- d3k agent-browser --cdp $(d3k cdp-port) open http://localhost:3000/page
40
- d3k agent-browser --cdp $(d3k cdp-port) snapshot -i # Get element refs (@e1, @e2)
41
- d3k agent-browser --cdp $(d3k cdp-port) click @e2
42
- d3k agent-browser --cdp $(d3k cdp-port) fill @e3 "text"
43
- d3k agent-browser --cdp $(d3k cdp-port) screenshot /tmp/shot.png
39
+ d3k cdp-port # Returns e.g. 9222
40
+ d3k agent-browser --cdp 9222 open http://localhost:3000/page
41
+ d3k agent-browser --cdp 9222 snapshot -i # Get element refs (@e1, @e2)
42
+ d3k agent-browser --cdp 9222 click @e2
43
+ d3k agent-browser --cdp 9222 fill @e3 "text"
44
+ d3k agent-browser --cdp 9222 screenshot /tmp/shot.png
44
45
  ```
45
46
 
46
47
  ## Fix Workflow
47
48
 
48
49
  1. `d3k errors --context` - See errors and what triggered them
49
50
  2. Fix the code
50
- 3. `d3k agent-browser --cdp $(d3k cdp-port) open <url>` then `click @e1` to replay
51
+ 3. Run `d3k cdp-port` to get the port, then `d3k agent-browser --cdp <port> open <url>` then `click @e1` to replay
51
52
  4. `d3k errors` - Verify fix worked
52
53
 
53
54
  ## Creating PRs with Before/After Screenshots
54
55
 
55
56
  When creating a PR for visual changes, **always capture before/after screenshots** to show the impact:
56
57
 
57
- 1. **Before making changes**, screenshot the production site:
58
+ 1. **Before making changes**, screenshot the production site (run `d3k cdp-port` first to get the port):
58
59
  ```bash
59
- d3k agent-browser --cdp $(d3k cdp-port) open https://production-url.com/affected-page
60
- d3k agent-browser --cdp $(d3k cdp-port) screenshot /tmp/before.png
60
+ d3k agent-browser --cdp <port> open https://production-url.com/affected-page
61
+ d3k agent-browser --cdp <port> screenshot /tmp/before.png
61
62
  ```
62
63
 
63
64
  2. **After making changes**, screenshot localhost:
64
65
  ```bash
65
- d3k agent-browser --cdp $(d3k cdp-port) open http://localhost:3000/affected-page
66
- d3k agent-browser --cdp $(d3k cdp-port) screenshot /tmp/after.png
66
+ d3k agent-browser --cdp <port> open http://localhost:3000/affected-page
67
+ d3k agent-browser --cdp <port> screenshot /tmp/after.png
67
68
  ```
68
69
 
69
70
  3. **Or use the tooling API** to capture multiple routes at once:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dev3000",
3
- "version": "0.0.169",
3
+ "version": "0.0.170",
4
4
  "description": "AI-powered development tools with browser monitoring and skill integration",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -76,9 +76,9 @@
76
76
  "vitest": "^3.2.4"
77
77
  },
78
78
  "optionalDependencies": {
79
- "@d3k/darwin-arm64": "0.0.169",
80
- "@d3k/linux-x64": "0.0.169",
81
- "@d3k/windows-x64": "0.0.169",
79
+ "@d3k/darwin-arm64": "0.0.170",
80
+ "@d3k/linux-x64": "0.0.170",
81
+ "@d3k/windows-x64": "0.0.170",
82
82
  "@opentui/core-linux-x64": "^0.1.71"
83
83
  },
84
84
  "engines": {