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

Add frontend lockfile (package-lock.json or pnpm-lock.yaml) to repository #863

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

Context

Roadmap item: P2 - Frontend - Missing lockfile

The frontend has no committed lockfile. This leads to non-reproducible builds: different CI runs or developer machines may install different dependency versions, causing subtle bugs.

Work to do

  1. Determine which package manager is being used (npm or pnpm) by inspecting the frontend/ directory.
  2. Run npm install (or pnpm install) to generate the lockfile.
  3. Commit package-lock.json (or pnpm-lock.yaml) to the repository.
  4. Update .gitignore to ensure the lockfile is NOT ignored.
  5. Update README.md and the Dockerfile to use npm ci (or pnpm install --frozen-lockfile) for reproducible installs.

Acceptance criteria

  • A lockfile is committed under frontend/.
  • npm ci (or pnpm install --frozen-lockfile) succeeds from a clean checkout.
  • The Dockerfile uses the frozen install command.
## Context Roadmap item: P2 - Frontend - Missing lockfile The frontend has no committed lockfile. This leads to non-reproducible builds: different CI runs or developer machines may install different dependency versions, causing subtle bugs. ## Work to do 1. Determine which package manager is being used (npm or pnpm) by inspecting the `frontend/` directory. 2. Run `npm install` (or `pnpm install`) to generate the lockfile. 3. Commit `package-lock.json` (or `pnpm-lock.yaml`) to the repository. 4. Update `.gitignore` to ensure the lockfile is NOT ignored. 5. Update `README.md` and the `Dockerfile` to use `npm ci` (or `pnpm install --frozen-lockfile`) for reproducible installs. ## Acceptance criteria - A lockfile is committed under `frontend/`. - `npm ci` (or `pnpm install --frozen-lockfile`) succeeds from a clean checkout. - The Dockerfile uses the frozen install command.
AI-Manager added the P2agent-readysmallfeature labels 2026-03-29 04:22:58 +00:00
AI-Manager commented 2026-03-29 05:05:47 +00:00
Author
Owner
Copy Link
Copy Source

Resolved in codebase. frontend/package-lock.json exists in the repository. CI uses npm ci which requires a lockfile. Closing as implemented.

Resolved in codebase. frontend/package-lock.json exists in the repository. CI uses npm ci which requires a lockfile. Closing as implemented.
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 feature 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#863
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?