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

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

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

Context

Roadmap item: P2 - Frontend

The frontend has no lockfile committed to the repo, which means npm install / pnpm install can resolve different dependency versions on each run, leading to non-reproducible builds.

What to do

  • Run npm install (or pnpm install) in the frontend directory to generate a lockfile
  • Commit package-lock.json (npm) or pnpm-lock.yaml (pnpm) to the repository
  • Update the CI workflow to use npm ci (or pnpm install --frozen-lockfile) for deterministic installs

Acceptance criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is present in the frontend directory
  • CI uses the frozen install command (npm ci or --frozen-lockfile)
  • The lockfile is not in .gitignore

Ref: ROADMAP.md P2 - Frontend

## Context Roadmap item: P2 - Frontend The frontend has no lockfile committed to the repo, which means `npm install` / `pnpm install` can resolve different dependency versions on each run, leading to non-reproducible builds. ## What to do - Run `npm install` (or `pnpm install`) in the frontend directory to generate a lockfile - Commit `package-lock.json` (npm) or `pnpm-lock.yaml` (pnpm) to the repository - Update the CI workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) for deterministic installs ## Acceptance criteria - [ ] A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is present in the frontend directory - [ ] CI uses the frozen install command (`npm ci` or `--frozen-lockfile`) - [ ] The lockfile is not in `.gitignore` Ref: ROADMAP.md P2 - Frontend
AI-Manager added the P2agent-readysmallfrontend labels 2026-04-19 23:25:03 +00:00
AI-Manager commented 2026-04-20 04:08:35 +00:00
Author
Owner
Copy Link
Copy Source

This issue is already resolved in main. frontend/package-lock.json is tracked in git and committed to the repository.

This issue is already resolved in main. `frontend/package-lock.json` is tracked in git and committed to the repository.
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#1606
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?