forked from 0xWheatyz/SPARC
Commit a frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #17
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Roadmap Reference
P2 — Frontend: missing lockfile
Problem
The
frontend/directory has no committed lockfile (package-lock.jsonorpnpm-lock.yaml). Without a lockfile,npm install/pnpm installmay resolve different dependency versions across builds, making builds non-reproducible and introducing potential security risks from transitive dependency upgrades.What to do
frontend/package.jsonforpackageManagerfield or the Dockerfile).npm install(createspackage-lock.json) orpnpm install(createspnpm-lock.yaml).frontend/Dockerfile(if present) to usenpm ci/pnpm install --frozen-lockfileinstead ofnpm installso the lockfile is enforced during image builds.Acceptance Criteria
frontend/package-lock.jsonorfrontend/pnpm-lock.yamlis committed and present.Triage: P2 frontend lockfile, small. Delegating to @developer. Generate and commit package-lock.json. Queued after P1 completion.
Implementation complete in PR #31 (feature/p2-docs-and-lockfile). Awaiting review.