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

Feature: Commit frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #723

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

Summary

The frontend has no lockfile committed to the repository. This means npm install (or pnpm install) can produce different dependency versions on different machines and in CI, leading to non-reproducible builds.

What to do

  • Determine which package manager the project uses (npm or pnpm).
  • Generate the appropriate lockfile (package-lock.json for npm, pnpm-lock.yaml for pnpm).
  • Commit the lockfile.
  • Ensure CI uses npm ci (or pnpm install --frozen-lockfile) rather than npm install.
  • Update .gitignore to NOT ignore the lockfile if it currently does.

Acceptance Criteria

  • A lockfile is committed in the frontend/ directory.
  • npm ci (or equivalent frozen install) completes successfully in CI.
  • The lockfile is kept up to date (instructions added to CONTRIBUTING or README).

Reference

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

## Summary The frontend has no lockfile committed to the repository. This means `npm install` (or `pnpm install`) can produce different dependency versions on different machines and in CI, leading to non-reproducible builds. ## What to do - Determine which package manager the project uses (npm or pnpm). - Generate the appropriate lockfile (`package-lock.json` for npm, `pnpm-lock.yaml` for pnpm). - Commit the lockfile. - Ensure CI uses `npm ci` (or `pnpm install --frozen-lockfile`) rather than `npm install`. - Update `.gitignore` to NOT ignore the lockfile if it currently does. ## Acceptance Criteria - [ ] A lockfile is committed in the `frontend/` directory. - [ ] `npm ci` (or equivalent frozen install) completes successfully in CI. - [ ] The lockfile is kept up to date (instructions added to CONTRIBUTING or README). ## Reference Roadmap: P2 Frontend — Missing package-lock.json or pnpm-lock.yaml.
AI-Manager added the P2agent-readysmallfeature labels 2026-03-28 16:23:42 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-28 17:03:18 +00:00
AI-Manager commented 2026-03-28 17:06:01 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Already resolved. frontend/package-lock.json exists in the repository.

Closing as already implemented in the codebase.

[Repo Manager] Already resolved. frontend/package-lock.json exists in the repository. Closing as already implemented in the codebase.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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