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

Commit a frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #1206

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

Context

The frontend directory has no lockfile committed to the repository. This means npm install or pnpm install can resolve different dependency versions on different machines or CI runs, producing non-reproducible builds.

Roadmap reference: ROADMAP.md > P2 > Frontend > Missing package-lock.json or pnpm-lock.yaml

What to do

  1. Decide on a single package manager (npm or pnpm) for the project.
  2. Run npm install (or pnpm install) locally to generate the lockfile.
  3. Commit the lockfile (package-lock.json or pnpm-lock.yaml) to the repository.
  4. Update .gitignore to ensure the lockfile is tracked (remove any rule that ignores it).
  5. Update CI to use npm ci (or pnpm install --frozen-lockfile) so it enforces the lockfile.

Acceptance criteria

  • A lockfile is present in the frontend directory and committed to main.
  • CI installs dependencies using the frozen lockfile command.
  • npm ci (or equivalent) completes without errors in a clean environment.
## Context The frontend directory has no lockfile committed to the repository. This means `npm install` or `pnpm install` can resolve different dependency versions on different machines or CI runs, producing non-reproducible builds. Roadmap reference: ROADMAP.md > P2 > Frontend > Missing package-lock.json or pnpm-lock.yaml ## What to do 1. Decide on a single package manager (npm or pnpm) for the project. 2. Run `npm install` (or `pnpm install`) locally to generate the lockfile. 3. Commit the lockfile (`package-lock.json` or `pnpm-lock.yaml`) to the repository. 4. Update `.gitignore` to ensure the lockfile is tracked (remove any rule that ignores it). 5. Update CI to use `npm ci` (or `pnpm install --frozen-lockfile`) so it enforces the lockfile. ## Acceptance criteria - [ ] A lockfile is present in the frontend directory and committed to `main`. - [ ] CI installs dependencies using the frozen lockfile command. - [ ] `npm ci` (or equivalent) completes without errors in a clean environment.
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-30 04:24:14 +00:00
AI-Manager commented 2026-03-30 05:04:56 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved on main. frontend/package-lock.json exists and is committed to the repository, enabling reproducible npm ci builds (also used in the CI workflow). Closing as complete.

This issue has been resolved on main. `frontend/package-lock.json` exists and is committed to the repository, enabling reproducible `npm ci` builds (also used in the CI workflow). Closing as complete.
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 frontend 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#1206
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?