Commit b0f762b
authored
fix(ci): replace npm ci with npm install — lockfile drift unblocks validate (#62)
The build-validation/validate job has been failing on main since the
committed package-lock.json went out of sync with package.json. Specific
error:
npm error Invalid: lock file's picomatch@2.3.2 does not satisfy
picomatch@4.0.4
npm error Missing: picomatch@2.3.2 from lock file (×3)
Root cause: tailwindcss^3.4.19 pulls in two distinct picomatch consumers
at different tree depths — chokidar wants ^2.3.1 (top-level), tinyglobby
wants ^4.0.4 (nested). The lockfile has the nested tinyglobby/picomatch@4.0.4
entry but is missing the top-level picomatch@2.3.2 chokidar needs.
`npm ci` (strict) refuses to install with missing entries; `npm install`
(non-strict) regenerates the missing entries in-place during CI.
This is a band-aid, not the real fix:
- The real fix is the npm→Deno migration tracked in
hyperpolymath/standards#253 (panll is in scope for that umbrella).
- The band-aid keeps validate green until that migration lands.
- --no-audit --no-fund silences noise.
Notes:
- Caught during the wider follow-up triage from
hyperpolymath/snifs#30's CI gate work, when panll#61 (fake-SHA fix)
surfaced the preexisting validate failure.1 parent f0940f3 commit b0f762b
1 file changed
Lines changed: 10 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
41 | 41 | | |
42 | 42 | | |
43 | 43 | | |
44 | | - | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
45 | 54 | | |
46 | 55 | | |
47 | 56 | | |
| |||
0 commit comments