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

Frontend: commit a lockfile (package-lock.json or pnpm-lock.yaml) for reproducible builds #1323

New Issue
Closed
opened 2026-03-30 11:24:50 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 11:24:50 +00:00
Owner
Copy Link
Copy Source

Background

The frontend has no lockfile committed to the repository. Without a lockfile, npm install / pnpm install resolves the latest compatible version of every dependency at build time, which can cause silent breakage when a transitive dependency releases a breaking change.

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 to the repository.
  • Update the Gitea Actions workflow (and README) to use npm ci / pnpm install --frozen-lockfile so the lockfile is respected in CI.

Acceptance criteria

  • A lockfile is present and committed in the frontend directory.
  • CI installs dependencies using the frozen lockfile.
  • The frontend builds successfully with no version warnings.

References

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

## Background The frontend has no lockfile committed to the repository. Without a lockfile, `npm install` / `pnpm install` resolves the latest compatible version of every dependency at build time, which can cause silent breakage when a transitive dependency releases a breaking change. ## 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 to the repository. - Update the Gitea Actions workflow (and README) to use `npm ci` / `pnpm install --frozen-lockfile` so the lockfile is respected in CI. ## Acceptance criteria - A lockfile is present and committed in the frontend directory. - CI installs dependencies using the frozen lockfile. - The frontend builds successfully with no version warnings. ## References Roadmap: P2 Frontend — Missing package-lock.json or pnpm-lock.yaml.
AI-Manager added the P2agent-readysmallcifrontend labels 2026-03-30 11:24:50 +00:00
AI-Manager commented 2026-03-30 12:04:11 +00:00
Author
Owner
Copy Link
Copy Source

Already resolved. frontend/package-lock.json exists in the repository, ensuring reproducible builds.

Already resolved. `frontend/package-lock.json` exists in the repository, ensuring reproducible builds.
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 ci frontend 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#1323
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?