@smi-digital/create-smi-app 2.11.1 → 2.11.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smi-digital/create-smi-app",
-  "version": "2.11.1",
+  "version": "2.11.2",
   "description": "",
   "main": "dist/index.js",
   "bin": {

package/templates/integrations/strapi-astro/Dockerfile.backend.template

@@ -11,10 +11,13 @@ RUN apk update && apk add --no-cache build-base gcc autoconf automake zlib-dev l
 WORKDIR /opt/
 COPY package.json package-lock.json* ./
 RUN npm install -g node-gyp
-# Use `npm ci` for a deterministic install straight from the lockfile. This also
-# installs sharp's pinned prebuilt musl binary (@img/sharp-linuxmusl-x64), which
-# `npm install` skips when the lockfile was generated on another OS (npm/cli#4828).
-RUN npm config set fetch-retry-maxtimeout 600000 -g && npm ci
+# `npm ci` for a deterministic install from the lockfile. The --os/--libc/--cpu
+# flags force npm to install sharp's prebuilt musl binary (@img/sharp-linuxmusl-x64,
+# already pinned in the lockfile). Without them, npm skips it when the lockfile was
+# generated on another OS and sharp falls back to a failing source build. This is
+# sharp's documented workaround for npm bug #4828. Flags target linux x64 deploys;
+# change --cpu=arm64 for arm builds.
+RUN npm config set fetch-retry-maxtimeout 600000 -g && npm ci --os=linux --libc=musl --cpu=x64
 ENV PATH=/opt/node_modules/.bin:$PATH
 
 WORKDIR /opt/app
@@ -30,8 +33,8 @@ ENV NODE_ENV=${NODE_ENV}
 WORKDIR /opt/
 COPY package.json package-lock.json* ./
 RUN npm install -g node-gyp
-# Deterministic prod install from the lockfile (see builder stage note re: sharp).
-RUN npm config set fetch-retry-maxtimeout 600000 -g && npm ci --omit=dev
+# Deterministic prod install from the lockfile; same sharp/musl flags as builder.
+RUN npm config set fetch-retry-maxtimeout 600000 -g && npm ci --omit=dev --os=linux --libc=musl --cpu=x64
 ENV PATH=/opt/node_modules/.bin:$PATH
 
 WORKDIR /opt/app