leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Commit a frontend lockfile to ensure reproducible builds #82

New Issue
Closed
opened 2026-03-26 14:23:26 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-26 14:23:26 +00:00
Owner
Copy Link
Copy Source

Context

The frontend has no committed lockfile (package-lock.json or pnpm-lock.yaml). Without a lockfile, npm install / pnpm install can resolve different dependency versions at different times, leading to non-reproducible builds and CI surprises.

Work

  • Determine the package manager in use (npm or pnpm).
  • Run npm install (or pnpm install) locally to generate the lockfile.
  • Commit the lockfile to the repository.
  • Update .gitignore to ensure the lockfile is not excluded.
  • Verify CI installs using the lockfile (npm ci or pnpm install --frozen-lockfile).

Acceptance Criteria

  • package-lock.json or pnpm-lock.yaml is present in the repository.
  • CI uses the frozen/locked install command.
  • A fresh npm ci (or equivalent) on a clean environment installs the same dependency versions.

References

Roadmap: Frontend — missing lockfile.

## Context The frontend has no committed lockfile (`package-lock.json` or `pnpm-lock.yaml`). Without a lockfile, `npm install` / `pnpm install` can resolve different dependency versions at different times, leading to non-reproducible builds and CI surprises. ## Work - Determine the package manager in use (npm or pnpm). - Run `npm install` (or `pnpm install`) locally to generate the lockfile. - Commit the lockfile to the repository. - Update `.gitignore` to ensure the lockfile is not excluded. - Verify CI installs using the lockfile (`npm ci` or `pnpm install --frozen-lockfile`). ## Acceptance Criteria - `package-lock.json` or `pnpm-lock.yaml` is present in the repository. - CI uses the frozen/locked install command. - A fresh `npm ci` (or equivalent) on a clean environment installs the same dependency versions. ## References Roadmap: Frontend — missing lockfile.
AI-Manager added the P2agent-readysmall labels 2026-03-26 14:23:26 +00:00
AI-Manager commented 2026-03-26 15:06:23 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Frontend package-lock.json committed for reproducible builds. Implemented in PR #31 (merged).

Resolved. Frontend `package-lock.json` committed for reproducible builds. Implemented in PR #31 (merged).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#82
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?