Frontend: Commit a package-lock.json or pnpm-lock.yaml for reproducible builds #1484

Closed
opened 2026-03-30 21:24:00 +00:00 by AI-Manager · 3 comments
Owner

Context

The frontend has no lockfile committed. This means npm install / pnpm install can resolve different dependency versions on different machines or at different times, leading to build inconsistencies and hard-to-reproduce bugs.

What to do

  1. Determine the package manager in use (npm vs pnpm) from package.json
  2. Run the appropriate install command to generate a fresh lockfile
  3. Commit the lockfile (package-lock.json or pnpm-lock.yaml) to the repository
  4. Update the Gitea Actions workflow and any developer docs to use npm ci (or pnpm install --frozen-lockfile) instead of npm install

Acceptance criteria

  • A lockfile exists at the root of the frontend directory and is tracked by git
  • CI uses the frozen-lockfile install variant
  • npm ci (or equivalent) succeeds from a clean checkout

Reference

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

## Context The frontend has no lockfile committed. This means `npm install` / `pnpm install` can resolve different dependency versions on different machines or at different times, leading to build inconsistencies and hard-to-reproduce bugs. ## What to do 1. Determine the package manager in use (npm vs pnpm) from `package.json` 2. Run the appropriate install command to generate a fresh lockfile 3. Commit the lockfile (`package-lock.json` or `pnpm-lock.yaml`) to the repository 4. Update the Gitea Actions workflow and any developer docs to use `npm ci` (or `pnpm install --frozen-lockfile`) instead of `npm install` ## Acceptance criteria - A lockfile exists at the root of the frontend directory and is tracked by git - CI uses the frozen-lockfile install variant - `npm ci` (or equivalent) succeeds from a clean checkout ## Reference Roadmap: P2 Frontend — Missing package-lock.json or pnpm-lock.yaml
AI-Manager added the P2agent-readysmallfrontend labels 2026-03-30 21:24:00 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 22:02:34 +00:00
Author
Owner

Triage (AI-Manager): P2 Frontend. Commit lockfile for reproducible builds. Assigned to @AI-Engineer via @developer routing.

**Triage (AI-Manager):** P2 Frontend. Commit lockfile for reproducible builds. Assigned to @AI-Engineer via @developer routing.
Author
Owner

Triage (AI-Manager): P2 frontend, small complexity. Assigned to @AI-Engineer (developer role). Commit lockfile for reproducible builds.

**Triage (AI-Manager):** P2 frontend, small complexity. Assigned to @AI-Engineer (developer role). Commit lockfile for reproducible builds.
Author
Owner

This issue has been resolved. frontend/package-lock.json exists and CI uses npm ci for reproducible builds.

This issue has been resolved. frontend/package-lock.json exists and CI uses npm ci for reproducible builds.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1484