From aa9705882f0dbbee9e564545face4a8960f232cb Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Thu, 14 May 2026 21:01:29 -0400 Subject: [PATCH] fix: use npm install in Dockerfile frontend-builder stage (no lockfile) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Same fix as the CI workflow — `npm ci` requires package-lock.json and we don't track one. Missed this in the earlier CI fix. Local `docker compose up` builds now succeed past the frontend stage. Co-Authored-By: Claude Opus 4.7 (1M context) --- Dockerfile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index 80307bd..66bf33f 100644 --- a/Dockerfile +++ b/Dockerfile @@ -3,7 +3,10 @@ FROM node:22-alpine AS frontend-builder WORKDIR /build COPY frontend/package.json frontend/package-lock.json* ./ -RUN npm ci --no-audit --no-fund +# No package-lock.json is tracked yet (we don't run npm locally per +# feedback-no-local-runs), so `npm install` instead of `npm ci`. Flip to +# `npm ci` once a lockfile is committed. +RUN npm install --no-audit --no-fund COPY frontend/ ./ RUN npm run build