chrome-relay 0.7.0 → 0.7.1

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/dist/cli.js CHANGED
@@ -1419,7 +1419,7 @@ var init_dist = __esm({
1419
1419
  import { Command } from "commander";
1420
1420
 
1421
1421
  // src/index.ts
1422
- var CHROME_RELAY_VERSION = true ? "0.7.0" : "0.0.0-dev";
1422
+ var CHROME_RELAY_VERSION = true ? "0.7.1" : "0.0.0-dev";
1423
1423
 
1424
1424
  // src/commands/shared.ts
1425
1425
  init_dist();
@@ -1527,8 +1527,8 @@ function emitTargetOverride(kind, from, to) {
1527
1527
  }
1528
1528
  async function runToolImpl(name, args) {
1529
1529
  try {
1530
- const parsedArgs = isToolName(name) ? parseToolArgs(name, args) : args;
1531
- const result = await callTool(name, parsedArgs);
1530
+ if (isToolName(name)) parseToolArgs(name, args);
1531
+ const result = await callTool(name, args);
1532
1532
  if (typeof result === "string") {
1533
1533
  process.stdout.write(result + "\n");
1534
1534
  } else {
@@ -1856,6 +1856,9 @@ async function runDoctor() {
1856
1856
 
1857
1857
  // src/release-notes.ts
1858
1858
  var RELEASE_NOTES = {
1859
+ "0.7.1": [
1860
+ "Fix: `wait` failed with `invalid_arguments: got 0 conditions` when invoked through the CLI. Root cause: the CLI transmitted the PARSED tool args over the bridge, and chrome_wait's parser transforms its shape ({selector} -> {condition}), so the extension re-parsed a shape it doesn't accept. The CLI now validates locally but transmits raw args \u2014 parsers run on the same raw shape at both ends, as designed. No extension change needed; 0.7.0 extensions work."
1861
+ ],
1859
1862
  "0.7.0": [
1860
1863
  "`wait` \u2014 block until a condition holds: `wait <css|@ref>` (exists and visible), `wait --text <s>`, `wait --url <glob>`, `wait --load load|domcontentloaded|networkidle`, `wait --fn <js>`, or `wait <ms>` for a plain sleep. One condition per call; default 10s, capped 25s (under the transport timeout, so waits always resolve in their own round-trip). Timeout errors include the page's current state so no follow-up probe is needed.",
1861
1864
  "`snapshot --diff` \u2014 print only what changed since this tab's previous snapshot (unified hunks + an additions/removals count; ~100 tokens instead of a full re-read). The full snapshot is still taken and the ref map still refreshes \u2014 refs in the diff are current and clickable.",
package/dist/index.js CHANGED
@@ -1,5 +1,5 @@
1
1
  // src/index.ts
2
- var CHROME_RELAY_VERSION = true ? "0.7.0" : "0.0.0-dev";
2
+ var CHROME_RELAY_VERSION = true ? "0.7.1" : "0.0.0-dev";
3
3
  export {
4
4
  CHROME_RELAY_VERSION
5
5
  };
@@ -56,7 +56,7 @@ function toBridgeError(unknownErr, fallbackTool) {
56
56
  }
57
57
 
58
58
  // src/index.ts
59
- var CHROME_RELAY_VERSION = true ? "0.7.0" : "0.0.0-dev";
59
+ var CHROME_RELAY_VERSION = true ? "0.7.1" : "0.0.0-dev";
60
60
 
61
61
  // src/release-notes.ts
62
62
  function compareSemver(a, b) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "chrome-relay",
3
- "version": "0.7.0",
3
+ "version": "0.7.1",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",