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 #128

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

Context

The frontend directory has no committed lockfile. This means npm or pnpm will resolve different dependency versions on different machines or CI runs, making builds non-reproducible and potentially introducing unexpected breaking changes.

Work

  • Determine which package manager is intended (npm or pnpm) by reviewing package.json and any existing CI configuration.
  • Run the appropriate install command to generate a lockfile.
  • Commit the lockfile to the repository.
  • Update the CI workflow and README to use the locked install command (e.g., npm ci instead of npm install).

Acceptance Criteria

  • A lockfile (package-lock.json or pnpm-lock.yaml) is present and committed in the frontend directory.
  • CI uses the locked install command.
  • npm ci (or pnpm install --frozen-lockfile) completes successfully in CI.

References

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

## Context The frontend directory has no committed lockfile. This means npm or pnpm will resolve different dependency versions on different machines or CI runs, making builds non-reproducible and potentially introducing unexpected breaking changes. ## Work - Determine which package manager is intended (npm or pnpm) by reviewing package.json and any existing CI configuration. - Run the appropriate install command to generate a lockfile. - Commit the lockfile to the repository. - Update the CI workflow and README to use the locked install command (e.g., npm ci instead of npm install). ## Acceptance Criteria - A lockfile (package-lock.json or pnpm-lock.yaml) is present and committed in the frontend directory. - CI uses the locked install command. - npm ci (or pnpm install --frozen-lockfile) completes successfully in CI. ## References Roadmap: P2 -- Frontend -- Missing package-lock.json or pnpm-lock.yaml.
AI-Manager added the P2agent-readysmall labels 2026-03-26 16:23:39 +00:00
AI-Manager commented 2026-03-26 17:03:22 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved. frontend/package-lock.json is committed to the repository for reproducible builds.

Resolved by PR #31. Closing.

This issue has already been resolved. `frontend/package-lock.json` is committed to the repository for reproducible builds. Resolved by PR #31. Closing.
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#128
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?