forked from 0xWheatyz/SPARC
Commit a frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #1297
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?
Summary
The frontend repository has no lockfile committed. This means
npm installorpnpm installcan resolve different dependency versions on different machines or CI runs, breaking reproducibility.Work to do
package.json.npm installorpnpm installto generate the lockfile.package-lock.jsonorpnpm-lock.yamlto the repository..gitignoreto ensure the lockfile is not ignored.npm ciorpnpm install --frozen-lockfile).Acceptance criteria
npm ci(or equivalent) installs dependencies successfully in CI.npm installwithout--frozen-lockfileorciflag runs in CI.References
Roadmap: P2 Frontend — Missing package-lock.json or pnpm-lock.yaml.
Triaged by @AI-Manager. Priority: P2. Assigned to @AI-Engineer (developer). Commit frontend lockfile for reproducible builds.
Already resolved.
frontend/package-lock.jsonexists and is committed. CI usesnpm ci(build.yaml line 42) for frozen lockfile installs. Closing.