ci: package-lock.json out of sync on master — npm ci fails (postcss 8.5.31 in lock vs 8.5.32 required)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- ci-cd
Research direction
Start with package.json and package-lock.json, using the pinned npm version 10.9.4 through Corepack. Regenerate the lockfile with npm install --package-lock-only, then verify a cold npm ci succeeds. Check the diff is limited to the postcss resolution.
Written by the indexing model from the issue text.
Description
Problem
npm ci fails on a cold install from master (verified 2026-11-05, eciperay manager run for #410):
npm error `npm ci` can only install packages when your package.json and package-lock.json are in sync.
npm error Invalid: lock file's [email protected] does not satisfy [email protected]
Same failure class as #285 / #300 / #311 / #382 / #428: a dependency bump landed without the lockfile being regenerated by the pinned npm, so the lockfile's pinned postcss (8.5.31) no longer satisfies the range package.json resolves (8.5.32).
Fix
Regenerate package-lock.json with the pinned npm (npm install --package-lock-only, [email protected] via the packageManager field / Corepack), verify npm ci passes on a cold install, and confirm no unrelated lockfile churn (the Tamagui nested-layout trap does not apply here — postcss is not in the @spudly/ui subtree, but check the diff stays scoped to the postcss resolution).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 192
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from spudly/eciperay
-
blocker bug in_progress priority-p1 qa
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
spudly/eciperay#425 · 4 comments ·
Maintainers usually reply within 1 day
-
blocked needs_human priority-p2
Difficulty 2/5 Half a day Newbie friendliness 68/100
spudly/eciperay#31 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement in_progress priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 48/100
spudly/eciperay#419 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement in_progress priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 55/100
spudly/eciperay#417 · 2 comments ·
Maintainers usually reply within 1 day
-
blocked needs_human priority-p2
Difficulty 1/5 1-3 hours Newbie friendliness 10/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
appandflow/stim#5258 ·
Maintainers usually reply within 1 day
-
area/docs framework/hugo help wanted language/markdown
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 68/100
lingdojo/kana-dojo#33660 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
drizzle-team/drizzle-orm#6639 ·
Maintainers usually reply within 4 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100