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) #650

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

Context

Roadmap item: P2 Frontend — Reproducible Builds

The frontend repository has no lockfile committed. This means npm install (or equivalent) resolves to different dependency versions on different machines and in CI, leading to non-reproducible builds.

What to do

  • Determine which package manager the frontend uses (npm, yarn, or pnpm)
  • Generate the appropriate lockfile: npm install generates package-lock.json, pnpm install generates pnpm-lock.yaml
  • Commit the lockfile to the repository
  • Update the CI workflow to use npm ci (or pnpm install --frozen-lockfile) instead of npm install to enforce the lockfile

Acceptance criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is present at the frontend root and committed to git
  • CI uses the frozen/locked install command
  • npm ci (or equivalent) succeeds from a clean checkout
## Context Roadmap item: P2 Frontend — Reproducible Builds The frontend repository has no lockfile committed. This means `npm install` (or equivalent) resolves to different dependency versions on different machines and in CI, leading to non-reproducible builds. ## What to do - Determine which package manager the frontend uses (npm, yarn, or pnpm) - Generate the appropriate lockfile: `npm install` generates `package-lock.json`, `pnpm install` generates `pnpm-lock.yaml` - Commit the lockfile to the repository - Update the CI workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) instead of `npm install` to enforce the lockfile ## Acceptance criteria - A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is present at the frontend root and committed to git - CI uses the frozen/locked install command - `npm ci` (or equivalent) succeeds from a clean checkout
AI-Manager added the P2agent-readysmall labels 2026-03-28 12:23:30 +00:00
AI-Manager commented 2026-03-28 13:03:30 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already present. frontend/package-lock.json exists in the repository and is used by npm ci in the CI workflow.

Closing as already present. `frontend/package-lock.json` exists in the repository and is used by `npm ci` in the CI workflow.
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#650
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?