@surea11y/webdriverio 1.4.0 → 1.4.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.
Files changed (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +3 -4
package/README.md CHANGED
@@ -8,9 +8,9 @@ A WebdriverIO binding for [`@surea11y/core`](https://github.com/SureA11y/core)
8
8
  npm install @surea11y/webdriverio webdriverio
9
9
  ```
10
10
 
11
- `@surea11y/core` 1.12.0 or later comes with it as a peer dependency, as WebdriverIO does: npm 7 and later, and pnpm 8 and later, install it for you, so the line above is all you need. With Yarn 1 or npm 6, which don't install peers, add `@surea11y/core` to that line.
11
+ `@surea11y/core` 1.12.0 or later, the engine, comes with it as a regular dependency, so the line above is all you need, whatever your package manager.
12
12
 
13
- Being a peer means your project and this binding share one copy of core. That matters as soon as your project uses core directly, to write a SARIF log or an HTML report (`@surea11y/core/sarif`, `/report`), read the rule catalogue, or keep a baseline: those read results with the same core that produced them, so a report never labels a finding with another release's rules. It holds when you bring your own core too: a linked checkout (`file:../core`), a monorepo, a fork, or a pinned release. Before 1.4.0, core was a regular dependency, and a project whose core differed from the binding's got a second copy without a word; such a project needed `"overrides": { "@surea11y/core": "$@surea11y/core" }` in its `package.json`, which it can now drop.
13
+ If your project uses core directly too, to write a SARIF log or an HTML report (`@surea11y/core/sarif`, `/report`), read the rule catalogue, or keep a baseline, keep one copy of it, so those read results with the same core that produced them. A compatible range in your own `package.json` (`"@surea11y/core": "^1.12.0"`) is enough: npm installs core once. When yours can't match the binding's range, as with a linked checkout (`file:../core`) or a fork, add `"overrides": { "@surea11y/core": "$@surea11y/core" }` beside it, and the binding uses your copy, which needs to be 1.12.0 or later. 1.4.0 made core a peer dependency instead; 1.4.1 undoes that, because Yarn, npm 6 and npm with `legacy-peer-deps` don't install peers, and a project with an older core pinned couldn't install the binding at all.
14
14
 
15
15
  `webdriverio` v9 auto-manages a local `chromedriver` for you the first time it launches Chrome (no separate Selenium server, and no extra browser-download step needed) — so a fresh `npm install` is enough for `npm test` to launch a real headless Chrome on its own.
16
16
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@surea11y/webdriverio",
3
- "version": "1.4.0",
3
+ "version": "1.4.1",
4
4
  "description": "Accessibility (a11y, WCAG) checks for WebdriverIO tests: scan the live page with new A11yCoreBuilder({ browser }).analyze() and get only proven violations, with findings that need human review listed separately.",
5
5
  "keywords": [
6
6
  "accessibility",
@@ -47,14 +47,13 @@
47
47
  "LICENSE"
48
48
  ],
49
49
  "dependencies": {
50
- "@surea11y/binding-base": "^1.4.0"
50
+ "@surea11y/binding-base": "^1.4.0",
51
+ "@surea11y/core": "^1.12.0"
51
52
  },
52
53
  "peerDependencies": {
53
- "@surea11y/core": ">=1.12.0",
54
54
  "webdriverio": ">=8.0.0"
55
55
  },
56
56
  "devDependencies": {
57
- "@surea11y/core": "^1.12.0",
58
57
  "@wdio/cli": "^9.32.0",
59
58
  "@wdio/local-runner": "^9.32.0",
60
59
  "@wdio/mocha-framework": "^9.32.0",