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

Commit a frontend lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #318

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

Context

Roadmap item: P2 Frontend — missing lockfile

No lockfile is committed for the frontend. This means npm install / pnpm install can resolve different dependency versions on different machines, making builds non-reproducible and potentially introducing breaking changes silently.

Work Required

  • Determine which package manager is used (npm or pnpm) by checking package.json scripts and any existing tooling config
  • Run npm install or pnpm install to generate the lockfile
  • Commit package-lock.json (npm) or pnpm-lock.yaml (pnpm)
  • Update the CI workflow to use npm ci (or pnpm install --frozen-lockfile) so it fails if the lockfile is out of date
  • Add a note to the contributing docs

Acceptance Criteria

  • The lockfile is present and committed in the frontend directory
  • CI installs dependencies using the frozen/ci install command
  • A second npm ci run with an unmodified lockfile succeeds without modifying any files
## Context Roadmap item: P2 Frontend — missing lockfile No lockfile is committed for the frontend. This means `npm install` / `pnpm install` can resolve different dependency versions on different machines, making builds non-reproducible and potentially introducing breaking changes silently. ## Work Required - Determine which package manager is used (npm or pnpm) by checking `package.json` scripts and any existing tooling config - Run `npm install` or `pnpm install` to generate the lockfile - Commit `package-lock.json` (npm) or `pnpm-lock.yaml` (pnpm) - Update the CI workflow to use `npm ci` (or `pnpm install --frozen-lockfile`) so it fails if the lockfile is out of date - Add a note to the contributing docs ## Acceptance Criteria - The lockfile is present and committed in the frontend directory - CI installs dependencies using the frozen/ci install command - A second `npm ci` run with an unmodified lockfile succeeds without modifying any files
AI-Manager added the P2agent-readysmall labels 2026-03-27 12:24:08 +00:00
AI-Manager commented 2026-03-27 13:03:44 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the fork's main branch. Already implemented in PR #31. frontend/package-lock.json exists.

Closing as completed.

This issue has already been resolved in the fork's main branch. Already implemented in PR #31. frontend/package-lock.json exists. 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#318
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?