OpenPanel is an open-source web and product analytics platform, an open-source alternative to Mixpanel with optional self-hosting.
fix(build): restore pnpm 10 install behavior broken by the 11.23.0 bump
Carl-Gerhard Lindesvärd4e715348a95d
diff --git a/package.json b/package.jsonindex 3561bac5f..8d3681acf 100644--- a/package.json+++ b/package.json@@ -35,18 +35,6 @@"semver": "^7.5.4","typescript": "catalog:"},- "trustedDependencies": [- "@biomejs/biome",- "@prisma/client",- "@prisma/engines",- "bcrypt",- "esbuild",- "lodepng",- "msgpackr-extract",- "prisma",- "protobufjs",- "sharp"- ],"devDependencies": {"@biomejs/biome": "2.3.15","depcheck": "^1.4.7",diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yamlindex 9a71c29a8..319a3ef3b 100644--- a/pnpm-workspace.yaml+++ b/pnpm-workspace.yaml@@ -8,6 +8,15 @@ packages:patchedDependencies:nuqs: patches/nuqs.patch+# nuqs is an apps/start dependency, but the api and worker images install a+# subset of the workspace (their Dockerfiles copy only their own and their+# backend packages' package.json). The patch then matches nothing, and pnpm 11+# turned that from a warning into ERR_PNPM_UNUSED_PATCH, breaking both builds.+# This only tolerates a patch matching nothing — patch application FAILURES+# still always error in v11 (ignorePatchFailures was removed), so the start+# build still fails loudly if nuqs.patch stops applying cleanly.+allowUnusedPatches: true+overrides:rolldown: 1.0.0-beta.43esm-env: npm:esm-env-runtime@^0.1.0@@ -26,19 +35,34 @@ catalog:pino-pretty: ^13.1.3"@hyperdx/node-opentelemetry": ^0.10.3-# pnpm 11 replacement for build-script approval. true = matches the intent of-# the old root "trustedDependencies" list; false = keep the previous-# (ignored) behavior.+# pnpm 11 replacement for build-script approval.+#+# These are all false on purpose — it is what the images have always shipped.+# The root package.json "trustedDependencies" list these were modelled on is a+# Bun/Yarn field that pnpm has never read, and pnpm 10 stopped running+# dependency build scripts unless allowlisted via onlyBuiltDependencies, which+# this repo never set. So under pnpm 10.6.2 not one of these scripts ran, and+# the images worked anyway (prebuilt binaries + the explicit `pnpm rebuild` and+# `pnpm codegen` steps in the Dockerfiles do the real work).+#+# Flipping them to true was a live behavior change smuggled into the version+# bump, and it broke the dashboard build: the prod stage sets+# npm_config_build_from_source=true, so sharp's newly-running install script+# tried to compile via node-gyp and failed with "Please add node-gyp to your+# dependencies". msgpackr-extract/esbuild/prisma are the same class of risk in+# that stage.+#+# Enable one only with a build that proves it is needed.allowBuilds:- '@biomejs/biome': true+ '@biomejs/biome': false'@parcel/watcher': false- '@prisma/client': true- '@prisma/engines': true+ '@prisma/client': false+ '@prisma/engines': false'@tailwindcss/oxide': false- esbuild: true- msgpackr-extract: true- prisma: true- protobufjs: true- sharp: true+ esbuild: false+ msgpackr-extract: false+ prisma: false+ protobufjs: false+ sharp: falsesimple-git-hooks: falseworkerd: false