v3.6.1: no-v2ray launch pinning (strip proxy env, explicit --no-proxy-server / FF direct prefs), cross-platform browser discovery (Win/Linux/macOS incl. snap chromium), setup.mjs deploy self-check, README deploy docs
This commit is contained in:
@@ -14,6 +14,12 @@ The kit talks to the browser the way a person does: it *sees* the page (visible
|
||||
|
||||
## Install
|
||||
|
||||
Run the deploy self-check first — it finds your browsers, checks Node, ports, profile dirs and direct egress, then prints the exact integration steps (Windows, Linux and macOS):
|
||||
|
||||
```bash
|
||||
node setup.mjs # exit code 0 = ready to integrate
|
||||
```
|
||||
|
||||
Copy this package into your harness profile (or `pnpm install` it as a workspace link), then add to your composition:
|
||||
|
||||
```yaml
|
||||
@@ -45,9 +51,11 @@ Firefox (158+) exposes WebDriver BiDi on its debug port rather than CDP; the ada
|
||||
|
||||
Per-browser profiles: the user's real profile by default (`realProfile`), or isolated kit profiles under `~/.dsh/browser-profiles/edge-kit[-chrome|-firefox]`. If your everyday browser owns the profile, pass `relaunch: true` to restart it debuggable (logins survive) or set `profileDir`.
|
||||
|
||||
Browser discovery is cross-platform — Windows, Linux (apt **and** snap paths, including `chromium`) and macOS, for all three browsers; pass `executablePath` for anything exotic.
|
||||
|
||||
## Actions
|
||||
|
||||
`launch` · `attach` · `status` · `tabs` · `newTab` · `switchTab` · `closeTab` · `goto` · `back` · `forward` · `reload` · `see` · `click` · `clickAt` · `drag` · `video` · `type` · `press` · `scroll` · `waitFor` · `eval` · `screenshot` · `wait` · `close`
|
||||
`launch` · `attach` · `status` · `tabs` · `newTab` · `switchTab` · `closeTab` · `goto` · `back` · `forward` · `reload` · `see` · `click` · `clickAt` · `drag` · `video` · `type` · `press` · `scroll` · `waitFor` · `eval` · `screenshot` · `wait` · `proxy` · `close`
|
||||
|
||||
## Proxy support
|
||||
|
||||
@@ -57,6 +65,7 @@ Per-browser profiles: the user's real profile by default (`realProfile`), or iso
|
||||
- **set** — installs a list verbatim. One hop is handed to the browser directly (`--proxy-server`); two or more are **chained** through an in-kit local CONNECT forwarder (browser → 127.0.0.1 → hop1 → hop2 → … → origin), verified end-to-end before the switch — a rejected chain falls back to the fastest single hop (or errors, in `set`).
|
||||
- **status** — live re-probe of the current route; **clear** — direct traffic again. `chainTo` adds one chained hop behind the auto-pick.
|
||||
- The `proxyChain` setting preloads a chain into every launch; the native web seam (`web_fetch` / `web_search`) rides the same route.
|
||||
- **Fully built in** — no system/v2ray proxy anywhere in the path: probes use raw sockets, and launched browsers get explicit proxy state (`--proxy-server` when routing; `--no-proxy-server` / `network.proxy.type:0` when direct, with `HTTP(S)_PROXY`/`ALL_PROXY` stripped from the launch environment). A local v2ray can never silently capture the browser.
|
||||
|
||||
A proxy counts as *working* only when an echo comes back through it — no blind trust in proxy-list sites.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user