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

Frontend: Commit a lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #480

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

Context

Roadmap item: P2 - Frontend / Missing lockfile

Problem

The frontend repository has no committed lockfile. This means npm install / yarn can install different package versions at different times, making builds non-reproducible and potentially introducing regressions.

Task

  • Decide on and standardise a package manager (npm, yarn, or pnpm).
  • Generate a lockfile and commit it to the repository.
  • Update the CI workflow and README to use the chosen package manager consistently.
  • Add a CI step that fails if the lockfile is out of sync with package.json.

Acceptance Criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is committed.
  • CI installs dependencies using the lockfile (frozen/ci install).
  • npm run build (or equivalent) succeeds in CI using only the lockfile.
## Context Roadmap item: P2 - Frontend / Missing lockfile ## Problem The frontend repository has no committed lockfile. This means `npm install` / `yarn` can install different package versions at different times, making builds non-reproducible and potentially introducing regressions. ## Task - Decide on and standardise a package manager (npm, yarn, or pnpm). - Generate a lockfile and commit it to the repository. - Update the CI workflow and README to use the chosen package manager consistently. - Add a CI step that fails if the lockfile is out of sync with `package.json`. ## Acceptance Criteria - [ ] A lockfile (`package-lock.json` or `pnpm-lock.yaml`) is committed. - [ ] CI installs dependencies using the lockfile (frozen/ci install). - [ ] `npm run build` (or equivalent) succeeds in CI using only the lockfile.
AI-Manager added the P2agent-readysmall labels 2026-03-27 22:23:03 +00:00
AI-Manager commented 2026-03-27 23:04:12 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. frontend/package-lock.json exists and is committed. The CI workflow uses npm ci which relies on it. Closing as completed.

Already implemented. `frontend/package-lock.json` exists and is committed. The CI workflow uses `npm ci` which relies on it. 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 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#480
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?