spec-controller 0.1.0-alpha.88 → 0.1.0
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/README.md +2 -4
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -11,17 +11,15 @@ Requires Node ≥ 22. ESM only.
|
|
|
11
11
|
## Install
|
|
12
12
|
|
|
13
13
|
```
|
|
14
|
-
npm install -g spec-controller
|
|
14
|
+
npm install -g spec-controller
|
|
15
15
|
```
|
|
16
16
|
|
|
17
17
|
Or without installing anything:
|
|
18
18
|
|
|
19
19
|
```
|
|
20
|
-
npx spec-controller
|
|
20
|
+
npx spec-controller balance --help
|
|
21
21
|
```
|
|
22
22
|
|
|
23
|
-
`@alpha` is not optional until `0.1.0` publishes: a bare install resolves `latest`, which npm set to `0.1.0-alpha.1` on the first publish, and that version has no `--ci-steps` and no scenario code errors.
|
|
24
|
-
|
|
25
23
|
## Your first run
|
|
26
24
|
|
|
27
25
|
Point it at your scenarios and give it nothing else:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "spec-controller",
|
|
3
|
-
"version": "0.1.0
|
|
3
|
+
"version": "0.1.0",
|
|
4
4
|
"description": "Reconcile the behaviour your scenarios name against the evidence that actually ran — the deterministic `balance` CLI.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"reconciliation",
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"@cucumber/gherkin": "^41.0.0",
|
|
26
26
|
"@cucumber/messages": "^34.0.1",
|
|
27
27
|
"yaml": "^2.9.0",
|
|
28
|
-
"@3f-consulting/spec-controller-core": "0.1.0
|
|
28
|
+
"@3f-consulting/spec-controller-core": "0.1.0"
|
|
29
29
|
},
|
|
30
30
|
"publishConfig": {
|
|
31
31
|
"access": "public"
|