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

Add and commit a frontend lockfile (package-lock.json or pnpm-lock.yaml) #698

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

Context

Roadmap item: P2 Frontend - missing lockfile

The frontend has no committed lockfile. CI and developers may install different dependency versions, causing non-reproducible builds and hard-to-debug behavior.

Work to do

  • Determine the package manager in use (npm or pnpm) by checking package.json
  • Run npm install (or pnpm install) to generate the lockfile
  • 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
  • Update .gitignore to ensure the lockfile is not ignored

Acceptance criteria

  • package-lock.json or pnpm-lock.yaml is tracked in the repo
  • CI installs dependencies using the locked versions
  • A fresh git clone followed by npm ci produces an identical node_modules on any machine
## Context Roadmap item: P2 Frontend - missing lockfile The frontend has no committed lockfile. CI and developers may install different dependency versions, causing non-reproducible builds and hard-to-debug behavior. ## Work to do - Determine the package manager in use (npm or pnpm) by checking `package.json` - Run `npm install` (or `pnpm install`) to generate the lockfile - 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 - Update `.gitignore` to ensure the lockfile is not ignored ## Acceptance criteria - `package-lock.json` or `pnpm-lock.yaml` is tracked in the repo - CI installs dependencies using the locked versions - A fresh `git clone` followed by `npm ci` produces an identical `node_modules` on any machine
AI-Manager added the P2agent-readysmallinfra labels 2026-03-28 15:23:27 +00:00
AI-Manager commented 2026-03-28 16:04:07 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Frontend lockfile (package-lock.json) was committed in PR #31 (feature/p2-docs-and-lockfile). File exists at frontend/package-lock.json.

Closing as already implemented. Frontend lockfile (package-lock.json) was committed in PR #31 (feature/p2-docs-and-lockfile). File exists at frontend/package-lock.json.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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