laxy-verify 1.1.13 → 1.1.14
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 +24 -3
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -3,6 +3,11 @@
|
|
|
3
3
|
CLI verification for frontend apps.
|
|
4
4
|
|
|
5
5
|
`laxy-verify` runs production build checks, Lighthouse, tiered verify E2E, and plan-gated verification features for Free, Pro, and Pro+ accounts.
|
|
6
|
+
It is designed around three user questions:
|
|
7
|
+
|
|
8
|
+
- Free: "Is this likely to break right now?"
|
|
9
|
+
- Pro: "Is this strong enough to send to a client?"
|
|
10
|
+
- Pro+: "Can I call this release-ready with confidence?"
|
|
6
11
|
|
|
7
12
|
```bash
|
|
8
13
|
npx laxy-verify --init --run
|
|
@@ -71,6 +76,9 @@ npx laxy-verify logout
|
|
|
71
76
|
| Visual diff | No | No | Yes |
|
|
72
77
|
| Failure analysis signals | No | No | Yes |
|
|
73
78
|
|
|
79
|
+
Pro is for delivery verification.
|
|
80
|
+
Pro+ is for release-confidence verification with extra evidence before you say "ship it."
|
|
81
|
+
|
|
74
82
|
For CI, set `LAXY_TOKEN` instead of using interactive login.
|
|
75
83
|
|
|
76
84
|
```yaml
|
|
@@ -129,13 +137,25 @@ Each run writes `.laxy-result.json`.
|
|
|
129
137
|
|
|
130
138
|
```json
|
|
131
139
|
{
|
|
132
|
-
"grade": "
|
|
140
|
+
"grade": "Gold",
|
|
133
141
|
"timestamp": "2026-04-09T09:00:00Z",
|
|
134
142
|
"build": { "success": true, "durationMs": 12000, "errors": [] },
|
|
135
|
-
"e2e": { "passed":
|
|
143
|
+
"e2e": { "passed": 5, "failed": 0, "total": 5, "results": [] },
|
|
136
144
|
"lighthouse": { "performance": 82, "accessibility": 94, "seo": 90, "bestPractices": 92, "runs": 3 },
|
|
145
|
+
"multiViewport": {
|
|
146
|
+
"allPassed": true,
|
|
147
|
+
"summary": "Desktop, tablet, and mobile checks passed."
|
|
148
|
+
},
|
|
149
|
+
"visualDiff": {
|
|
150
|
+
"verdict": "pass",
|
|
151
|
+
"differencePercentage": 0
|
|
152
|
+
},
|
|
153
|
+
"verification": {
|
|
154
|
+
"tier": "pro_plus",
|
|
155
|
+
"report": { "verdict": "release-ready" }
|
|
156
|
+
},
|
|
137
157
|
"exitCode": 0,
|
|
138
|
-
"_plan": "
|
|
158
|
+
"_plan": "pro_plus"
|
|
139
159
|
}
|
|
140
160
|
```
|
|
141
161
|
|
|
@@ -144,6 +164,7 @@ Each run writes `.laxy-result.json`.
|
|
|
144
164
|
- Monorepos require targeting the app subdirectory explicitly.
|
|
145
165
|
- Dev-server-based Lighthouse can differ from production hosting.
|
|
146
166
|
- Pro+ visual diff and viewport checks increase runtime.
|
|
167
|
+
- Local verification is most stable on current LTS Node releases.
|
|
147
168
|
|
|
148
169
|
## License
|
|
149
170
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "laxy-verify",
|
|
3
|
-
"version": "1.1.
|
|
4
|
-
"description": "Frontend quality gate: build
|
|
3
|
+
"version": "1.1.14",
|
|
4
|
+
"description": "Frontend quality gate: build, Lighthouse, tiered E2E, and release-confidence verification",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "commonjs",
|
|
7
7
|
"bin": {
|