browserscale-ts 1.7.0 → 1.7.1

package/README.md

@@ -78,14 +78,17 @@ Rent an isolated browser session in seconds, automate it with human-like input,
   offset, with live form state (typed values, checkbox state, `<select>`
   options) and a node handle to act on. A model reasons over what matters
   instead of raw HTML, and doesn't need a JS round-trip to ask where it is.
-- **Scripts that run inside the browser** — `runScript` sends JavaScript to the
-  session and runs it in the browser process itself, with a `browser` object
-  giving it the same operations this SDK exposes — but as local calls rather than
-  network round trips, so a loop that polls or walks a list costs microseconds
-  per step instead of tens of milliseconds. The log streams back as the script
-  produces it. `startScript` leaves a script running without the caller, which is
-  how work outlives the process that started it, and `followScript` attaches to
-  one already under way.
+- **Scripts that run beside the browser** — `runScript` sends JavaScript to the
+  session, where it runs in an isolate of its own and reaches the document
+  through the engine: a cross-origin `<iframe>` is read as plain
+  `contentDocument` with no frame ids anywhere, values come back as live objects
+  you can assign to rather than snapshots, an element can be handed straight to
+  `browser.click`, and the page sees nothing injected. Steps cost microseconds
+  rather than network round trips, so loops are affordable. The log streams back
+  as the script produces it; `startScript` leaves a script running without the
+  caller, which is how work outlives the process that started it, and
+  `followScript` attaches to one already under way. A guide for it is still to
+  come.
 - **Sessions you can find again** — `listBrowsers` reports what an API key is
   paying for: ids, proxy, egress address and remaining rental. A session
   therefore outlives the process that rented it — recover it after a restart, or
@@ -152,7 +155,7 @@ reports the element that occluded the click.
 | `browser.click(target, opts?)` | Human-like click; throws a rich `ClickError` on failure. |
 | `browser.fill(target, text, opts?)` | Per-key typing that fires real input events; `insertText` for bulk commit. |
 | `browser.evaluate(expr)` | Run JS in the page/frame and get a typed value back. |
-| `browser.runScript(source)` | Run JavaScript in the browser process, where every operation is a local call; `startScript` leaves it running, `followScript` watches one already going. |
+| `browser.runScript(source)` | Run JavaScript beside the browser, where cross-origin frames are property access and every step is local; `startScript` leaves it running, `followScript` watches one already going. |
 | `browser.getObservation(opts?)` | Compact, node-handle-tagged view of the visible page across frames; `opts` tunes budgets and format. |
 | `browser.captureNetwork(opts, onExchange)` | Stream every request the session completes, optionally with response bodies. |
 | `browser.mirrorDom(opts, onChange, onResync?)` | Live, incrementally updated copy of the page's DOM across every frame. |

package/dist/browserscale.browser.js

@@ -7229,12 +7229,14 @@ var CloudBrowser = class {
   /**
    * Runs `source` in the session's browser and waits for it to finish.
    *
-   * The script executes in a V8 isolate inside the browser process, not in the
-   * page, and reaches the same operations this SDK exposes through a `browser`
-   * object it is handed. The difference is cost: each call is a function call in
-   * the browser rather than a network round trip, so work that is chatty by
-   * nature — polling for a selector, walking a list, following pagination —
-   * runs in microseconds per step instead of tens of milliseconds.
+   * The script runs beside the browser, in a V8 isolate of its own rather than
+   * in the page, and reaches the document through the engine: a cross-origin
+   * `<iframe>` is read as plain `contentDocument` with no frame ids anywhere,
+   * values come back as live objects it can assign to rather than snapshots, an
+   * element can be handed straight to `browser.click`, and the page sees nothing
+   * injected. Steps cost microseconds rather than network round trips, so work
+   * that is chatty by nature — polling for a selector, walking a list,
+   * following pagination — is affordable there. A guide for it is still to come.
    *
    * This waits for as long as the script runs, and cannot be bounded: the run
    * id needed to cancel only arrives with the reply. Use

package/dist/client.d.ts

@@ -1265,12 +1265,14 @@ export declare class CloudBrowser {
     /**
      * Runs `source` in the session's browser and waits for it to finish.
      *
-     * The script executes in a V8 isolate inside the browser process, not in the
-     * page, and reaches the same operations this SDK exposes through a `browser`
-     * object it is handed. The difference is cost: each call is a function call in
-     * the browser rather than a network round trip, so work that is chatty by
-     * nature — polling for a selector, walking a list, following pagination —
-     * runs in microseconds per step instead of tens of milliseconds.
+     * The script runs beside the browser, in a V8 isolate of its own rather than
+     * in the page, and reaches the document through the engine: a cross-origin
+     * `<iframe>` is read as plain `contentDocument` with no frame ids anywhere,
+     * values come back as live objects it can assign to rather than snapshots, an
+     * element can be handed straight to `browser.click`, and the page sees nothing
+     * injected. Steps cost microseconds rather than network round trips, so work
+     * that is chatty by nature — polling for a selector, walking a list,
+     * following pagination — is affordable there. A guide for it is still to come.
      *
      * This waits for as long as the script runs, and cannot be bounded: the run
      * id needed to cancel only arrives with the reply. Use

package/dist/client.js

@@ -2003,12 +2003,14 @@ export class CloudBrowser {
     /**
      * Runs `source` in the session's browser and waits for it to finish.
      *
-     * The script executes in a V8 isolate inside the browser process, not in the
-     * page, and reaches the same operations this SDK exposes through a `browser`
-     * object it is handed. The difference is cost: each call is a function call in
-     * the browser rather than a network round trip, so work that is chatty by
-     * nature — polling for a selector, walking a list, following pagination —
-     * runs in microseconds per step instead of tens of milliseconds.
+     * The script runs beside the browser, in a V8 isolate of its own rather than
+     * in the page, and reaches the document through the engine: a cross-origin
+     * `<iframe>` is read as plain `contentDocument` with no frame ids anywhere,
+     * values come back as live objects it can assign to rather than snapshots, an
+     * element can be handed straight to `browser.click`, and the page sees nothing
+     * injected. Steps cost microseconds rather than network round trips, so work
+     * that is chatty by nature — polling for a selector, walking a list,
+     * following pagination — is affordable there. A guide for it is still to come.
      *
      * This waits for as long as the script runs, and cannot be bounded: the run
      * id needed to cancel only arrives with the reply. Use

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "browserscale-ts",
-  "version": "1.7.0",
+  "version": "1.7.1",
   "description": "Official SDK for browserscale — undetected stealth browsers in the cloud. Rent real Chromium sessions with unique fingerprints, built-in proxies, captcha solving, human-like input and live video — scale web scraping and automation without running a single browser yourself.",
   "main": "dist/index.js",
   "type": "module",