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

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

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

Context

Roadmap reference: P2 - Missing package-lock.json or pnpm-lock.yaml

The frontend has no lockfile committed to the repository. This means npm install / pnpm install will resolve potentially different dependency versions on each fresh build, making builds non-reproducible and harder to debug.

What to do

  1. Determine which package manager the project uses (npm or pnpm)
  2. Run npm install (or pnpm install) in the frontend directory to generate the lockfile
  3. Commit the generated lockfile (package-lock.json or pnpm-lock.yaml)
  4. Update .gitignore to ensure the lockfile is NOT ignored
  5. Verify the CI build succeeds with the locked dependencies

Acceptance criteria

  • A lockfile is committed to the repository
  • npm ci (or pnpm install --frozen-lockfile) succeeds in a fresh environment
  • The lockfile is not in .gitignore
## Context Roadmap reference: P2 - Missing package-lock.json or pnpm-lock.yaml The frontend has no lockfile committed to the repository. This means `npm install` / `pnpm install` will resolve potentially different dependency versions on each fresh build, making builds non-reproducible and harder to debug. ## What to do 1. Determine which package manager the project uses (npm or pnpm) 2. Run `npm install` (or `pnpm install`) in the frontend directory to generate the lockfile 3. Commit the generated lockfile (`package-lock.json` or `pnpm-lock.yaml`) 4. Update `.gitignore` to ensure the lockfile is NOT ignored 5. Verify the CI build succeeds with the locked dependencies ## Acceptance criteria - [ ] A lockfile is committed to the repository - [ ] `npm ci` (or `pnpm install --frozen-lockfile`) succeeds in a fresh environment - [ ] The lockfile is not in `.gitignore`
AI-Manager added the P2agent-readysmallinfra labels 2026-03-28 17:23:39 +00:00
AI-Manager commented 2026-03-28 18:03:51 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. frontend/package-lock.json is committed. CI workflow uses npm ci for reproducible installs.

**Resolved.** `frontend/package-lock.json` is committed. CI workflow uses `npm ci` for reproducible installs.
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 infra 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#747
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?