Skip to content

fix: pin @mat3ra/prove devDependency to unstick stale lockfile resolution - #12

Merged
k0stik merged 1 commit into
mainfrom
fix/prove-lockfile-pin
Aug 19, 2026
Merged

fix: pin @mat3ra/prove devDependency to unstick stale lockfile resolution#12
k0stik merged 1 commit into
mainfrom
fix/prove-lockfile-pin

Conversation

@k0stik

@k0stik k0stik commented Aug 19, 2026

Copy link
Copy Markdown
Member

Summary

  • `package-lock.json` had `@mat3ra/prove` resolved to a stale `2026.6.12-0` (predating prove's `@mat3ra/cove` rename), left over from before prove was ever added to `devDependencies` alongside jove's other `@mat3ra/*` deps.
  • Since `dependencies` only specifies `"*"` for prove, `npm ci` kept honoring the old lockfile entry indefinitely - this is why `deploy-bundle` kept failing with `Rollup failed to resolve import "@exabyte-io/cove.js/dist/theme/provider"` even after a clean rerun; the registry itself always had the correct `2026.8.19-0` content.
  • Added an explicit `@mat3ra/prove: 2026.8.19-0` pin to `devDependencies` (matching the pattern already used for every other `@mat3ra/*` dep in this file) and regenerated the lockfile.

Test plan

  • `npm run transpile` passes
  • `npm run build:standalone` passes locally, no cove-related resolution errors
  • CI `deploy-bundle` job goes green

… entry

package-lock.json had prove locked to a stale 2026.6.12-0 (pre-cove-rename)
resolution left over from before prove ever appeared in devDependencies,
which npm ci kept honoring regardless of the "*" range in dependencies -
causing deploy-bundle to bundle prove's old @exabyte-io/cove.js import.
@k0stik
k0stik merged commit ad17d5a into main Aug 19, 2026
5 checks passed
@k0stik
k0stik deleted the fix/prove-lockfile-pin branch August 19, 2026 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant