craftdriver 1.0.4 → 1.1.1

package/docs/zero-config-drivers.md

@@ -24,15 +24,24 @@ CraftDriver checks for the driver in this order:
 | ---- | ----------------------------------------------------------------------- |
 | 1    | Explicit `ChromeService` / `FirefoxService` configuration               |
 | 2    | Environment variables such as `CHROMEDRIVER_PATH` or `GECKODRIVER_PATH` |
-| 3    | Project-local binaries in `node_modules/.bin`                           |
-| 4    | Binaries already available on `PATH`                                    |
-| 5    | Auto-resolved and cached driver matching the installed browser          |
+| 3    | Known CI-provided driver directories (e.g. GitHub Actions' `CHROMEWEBDRIVER` / `GECKOWEBDRIVER`) |
+| 4    | Project-local binaries in `node_modules/.bin`                           |
+| 5    | Binaries already available on `PATH`                                    |
+| 6    | Auto-resolved and cached driver matching the installed browser          |
 
 If a browser update leaves a cached driver stale, CraftDriver retries once with a refreshed driver instead of making you clear the cache manually.
 
 ## CI Friendly
 
-The default setup works well on CI runners that already include Chrome or Firefox. For stricter environments, you can pin the driver path or run offline:
+The default setup works well on CI runners that already include Chrome or
+Firefox. On **GitHub Actions** specifically, craftdriver auto-detects the
+runner's own pre-installed, version-matched driver out of the box (via
+`CHROMEWEBDRIVER` / `GECKOWEBDRIVER`) — no configuration needed, and it's
+faster than the fallback probes since it skips version detection entirely (see
+[Driver Configuration → CI platform detection](./driver-configuration.md#ci-platform-detection)).
+
+For platforms without built-in detection, or to pin a driver other than the
+runner's default, set the path manually:
 
 ```bash
 CRAFTDRIVER_CHROMEDRIVER_PATH=/usr/bin/chromedriver npm test
@@ -48,5 +57,8 @@ Manual configuration is useful when:
 - network access is blocked
 - you need custom driver logging
 - you want to avoid any version detection during launch
+- you're launching a non-default Chrome/Chromium/Firefox build via
+  `browserPath` / `CRAFTDRIVER_CHROME_PATH` — see
+  [Driver Configuration → Browser Binary Configuration](./driver-configuration.md#browser-binary-configuration)
 
 See [Driver Configuration](./driver-configuration.md) for the full reference.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "craftdriver",
-  "version": "1.0.4",
+  "version": "1.1.1",
   "description": "Modern WebDriver automation library for NodeJS",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -17,14 +17,18 @@
     "test:firefox": "BROWSER_NAME=firefox HEADLESS=true vitest run --maxWorkers=2",
     "test:chrome": "BROWSER_NAME=chrome vitest run",
     "test:chromium": "BROWSER_NAME=chromium vitest run",
+    "test:recipes": "HEADLESS=true vitest run --config vitest.recipes.config.ts",
     "bench": "HEADLESS=true vitest run --config vitest.perf.config.ts",
     "bench:realapp": "HEADLESS=true vitest run --config vitest.perf.realapp.config.ts",
     "clean": "rimraf dist",
     "serve": "http-server ./examples -a 127.0.0.1 -p 8080 -c-1 --cors",
     "examples:start": "npm run serve",
+    "docs:examples": "node scripts/copy-examples.mjs",
     "docs:api": "node scripts/gen-api-reference.mjs",
     "docs:api:check": "node scripts/gen-api-reference.mjs --check",
+    "predocs:dev": "npm run docs:examples",
     "docs:dev": "vitepress dev docs",
+    "predocs:build": "npm run docs:examples",
     "docs:build": "vitepress build docs",
     "docs:preview": "vitepress preview docs",
     "docs:check": "npm run docs:api:check && npm run docs:build",