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

Add frontend lockfile (package-lock.json or pnpm-lock.yaml) to repository #1509

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

Context

Roadmap item: P2 Frontend — lockfile

The frontend directory has no committed lockfile. Without one, npm install / pnpm install resolves different package versions on different machines and CI runs, making builds non-reproducible.

What to do

  1. In the frontend directory, run npm install (or pnpm install if pnpm is the intended package manager) to generate a lockfile.
  2. Commit package-lock.json (or pnpm-lock.yaml) to the repository.
  3. Update .gitignore to ensure the lockfile is NOT ignored.
  4. Update the docker-compose.yml frontend build step (if applicable) to use npm ci instead of npm install for reproducible installs.
  5. Verify the Gitea Actions build workflow uses the lockfile (npm ci).

Acceptance criteria

  • A lockfile is committed and up to date with package.json
  • .gitignore does not exclude the lockfile
  • CI uses npm ci (or equivalent) for reproducible installs
  • Frontend builds successfully after the change
## Context Roadmap item: P2 Frontend — lockfile The frontend directory has no committed lockfile. Without one, `npm install` / `pnpm install` resolves different package versions on different machines and CI runs, making builds non-reproducible. ## What to do 1. In the frontend directory, run `npm install` (or `pnpm install` if pnpm is the intended package manager) to generate a lockfile. 2. Commit `package-lock.json` (or `pnpm-lock.yaml`) to the repository. 3. Update `.gitignore` to ensure the lockfile is NOT ignored. 4. Update the `docker-compose.yml` frontend build step (if applicable) to use `npm ci` instead of `npm install` for reproducible installs. 5. Verify the Gitea Actions build workflow uses the lockfile (`npm ci`). ## Acceptance criteria - [ ] A lockfile is committed and up to date with `package.json` - [ ] `.gitignore` does not exclude the lockfile - [ ] CI uses `npm ci` (or equivalent) for reproducible installs - [ ] Frontend builds successfully after the change
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-31 00:24:29 +00:00
AI-Manager commented 2026-03-31 01:04:15 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is already resolved. frontend/package-lock.json exists in the repository. CI workflows use npm ci which relies on it. Closing as complete.

[Repo Manager] This issue is already resolved. `frontend/package-lock.json` exists in the repository. CI workflows use `npm ci` which relies on it. Closing as complete.
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 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#1509
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?