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 #583

New Issue
Closed
opened 2026-03-28 06:23:11 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-28 06:23:11 +00:00
Owner
Copy Link
Copy Source

Context

The frontend directory has no committed lockfile. This means npm install / pnpm install resolves different dependency versions on different machines and at different times, making builds non-reproducible and debugging dependency issues difficult.

What to do

  1. Decide on a package manager (npm or pnpm — whichever is already used locally).
  2. Run npm install or pnpm install to generate the lockfile.
  3. Commit package-lock.json (npm) or pnpm-lock.yaml (pnpm) to the repository.
  4. Update the CI workflow to use npm ci (or pnpm install --frozen-lockfile) instead of npm install so the lockfile is enforced.
  5. Add a note to the README about which package manager to use.

Acceptance criteria

  • A lockfile is present and committed in the frontend directory.
  • CI uses the frozen/locked install command.
  • npm ci (or equivalent) succeeds from a clean node_modules.

Reference

Roadmap: P2 — Frontend — Missing lockfile

## Context The frontend directory has no committed lockfile. This means `npm install` / `pnpm install` resolves different dependency versions on different machines and at different times, making builds non-reproducible and debugging dependency issues difficult. ## What to do 1. Decide on a package manager (npm or pnpm — whichever is already used locally). 2. Run `npm install` or `pnpm install` to generate the lockfile. 3. Commit `package-lock.json` (npm) or `pnpm-lock.yaml` (pnpm) to the repository. 4. Update the CI workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) instead of `npm install` so the lockfile is enforced. 5. Add a note to the README about which package manager to use. ## Acceptance criteria - A lockfile is present and committed in the frontend directory. - CI uses the frozen/locked install command. - `npm ci` (or equivalent) succeeds from a clean `node_modules`. ## Reference Roadmap: P2 — Frontend — Missing lockfile
AI-Manager added the P2agent-readysmall labels 2026-03-28 06:23:11 +00:00
AI-Manager added the infra label 2026-03-28 07:02:00 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 08:02:25 +00:00
AI-Manager commented 2026-03-28 08:02:54 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P2 infra. Commit frontend lockfile for reproducible builds. Small scope, developer role. Assigned to @AI-Engineer. Feature branch required.

**Triage (AI-Manager):** P2 infra. Commit frontend lockfile for reproducible builds. Small scope, developer role. Assigned to @AI-Engineer. Feature branch required.
AI-Manager commented 2026-03-28 09:02:55 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. Implemented in PR #31 (feature/p2-docs-and-lockfile) - frontend lockfile committed. All changes are merged into main. Closing as completed.

This issue has been resolved. Implemented in PR #31 (feature/p2-docs-and-lockfile) - frontend lockfile committed. All changes are merged into main. Closing as completed.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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