fix(docker): drop --frozen-lockfile from install step per pnpm fetch docs

The pnpm fetch docs recommend `pnpm install -r --offline` without --frozen-lockfile. The --offline flag already enforces no registry access, making --frozen-lockfile redundant. https://pnpm.io/cli/fetch
fix(docker): resolve pnpm fetch crash with patchedDependencies
2026-07-13 20:24:59 +02:00 · 2026-07-13 20:06:28 +02:00
1 changed files with 15 additions and 2 deletions
@@ -9,12 +9,25 @@ RUN apk add --no-cache libc6-compat curl bash && apk update
 RUN corepack enable pnpm
 COPY pnpm-lock.yaml pnpm-workspace.yaml package.json ./
 COPY patches ./patches
+# Workaround for pnpm/pnpm#5268: pnpm fetch crashes when patchedDependencies
+# are configured with nodeLinker: hoisted. The applyPatchToDir function tries
+# to chdir into node_modules/<pkg> which doesn't exist during fetch (only the
+# content-addressable store is populated). By temporarily switching to the
+# isolated linker, patches apply inside the virtual store (node_modules/.pnpm/...)
+# which IS created by pnpm fetch. The original hoisted linker is restored
+# before the install step so the final node_modules layout stays flat.
 RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm config set store-dir /pnpm/store && pnpm fetch
+    pnpm config set store-dir /pnpm/store && \
+    sed -i 's/nodeLinker: hoisted/nodeLinker: isolated/' pnpm-workspace.yaml && \
+    pnpm fetch && \
+    sed -i 's/nodeLinker: isolated/nodeLinker: hoisted/' pnpm-workspace.yaml

 COPY . .
+# Follow the pnpm fetch pattern from https://pnpm.io/cli/fetch
+# --offline enforces no registry access (all packages are in the store from fetch)
+# --frozen-lockfile is omitted as recommended by the pnpm fetch docs
 RUN --mount=type=cache,id=pnpm-store,target=/pnpm/store \
-    pnpm install --recursive --offline --frozen-lockfile
+    pnpm install --recursive --offline

 ARG SKIP_ENV_VALIDATION='true'
 ARG CI='true'