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

Commit a frontend package lockfile for reproducible builds #813

New Issue
Closed
opened 2026-03-29 01:23:30 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 01:23:30 +00:00
Owner
Copy Link
Copy Source

Background

The frontend has no package-lock.json or pnpm-lock.yaml committed. This means npm install / pnpm install can install different dependency versions on different machines or in CI, causing hard-to-debug inconsistencies.

What to do

  1. Determine the package manager in use (npm or pnpm)
  2. Run the appropriate install command to generate the lockfile
  3. Commit the lockfile to the repository
  4. Update the CI workflow and README to use npm ci / pnpm install --frozen-lockfile instead of npm install to enforce lockfile usage
  5. Add the lockfile to .gitignore exclusion list (i.e., ensure it is NOT in .gitignore)

Acceptance criteria

  • package-lock.json or pnpm-lock.yaml is present and committed
  • CI installs dependencies using the frozen/locked form of the install command
  • Subsequent clean installs produce the same dependency tree

References

Roadmap item: P2 Frontend -- Missing package-lock.json or pnpm-lock.yaml

## Background The frontend has no `package-lock.json` or `pnpm-lock.yaml` committed. This means `npm install` / `pnpm install` can install different dependency versions on different machines or in CI, causing hard-to-debug inconsistencies. ## What to do 1. Determine the package manager in use (npm or pnpm) 2. Run the appropriate install command to generate the lockfile 3. Commit the lockfile to the repository 4. Update the CI workflow and README to use `npm ci` / `pnpm install --frozen-lockfile` instead of `npm install` to enforce lockfile usage 5. Add the lockfile to `.gitignore` exclusion list (i.e., ensure it is NOT in `.gitignore`) ## Acceptance criteria - `package-lock.json` or `pnpm-lock.yaml` is present and committed - CI installs dependencies using the frozen/locked form of the install command - Subsequent clean installs produce the same dependency tree ## References Roadmap item: P2 Frontend -- Missing `package-lock.json` or `pnpm-lock.yaml`
AI-Manager added the P2agent-readysmallfeature labels 2026-03-29 01:23:30 +00:00
AI-Manager commented 2026-03-29 02:06:14 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). Closing as completed.

This issue has already been resolved and merged into main via PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). Closing as completed.
AI-Manager commented 2026-03-29 02:07:13 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). Closing as completed.

This issue has already been resolved and merged into main via PR #31 (docs: patent PDF storage docs, FileNotFoundError, frontend lockfile). 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 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#813
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?