From bfee58661d380ce93293ad130c10e9e826226b2b Mon Sep 17 00:00:00 2001 From: Evan Vetere Date: Tue, 17 Nov 2026 14:52:46 -0500 Subject: [PATCH] fix: Let npm 12 read bundled deps in Renovate locks Renovate's lockfile step fails with EALLOWREMOTE in every repository on Tailwind 4, so its pull requests carry a stale package-lock.json and fail npm ci. With --package-lock-only, npm 12 unpacks each package that declares bundleDependencies to read the bundle, and that fetch skips the registry-tarball exemption from the default allow-remote=none (npm/cli#9800). Tailwind's optional @tailwindcss/oxide-wasm32-wasi is such a package, served from registry.npmjs.org. Set allow-remote=all in the .npmrc Renovate writes for its own lockfile step. Repositories keep their own .npmrc, so npm ci in CI keeps npm 12's default refusal and still rejects a lockfile that resolves to a URL. --- renovate-config.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/renovate-config.json b/renovate-config.json index 8d27c19..8305242 100644 --- a/renovate-config.json +++ b/renovate-config.json @@ -1,12 +1,12 @@ { "$schema": "https://docs.renovatebot.com/renovate-schema.json", - "description": "Datum's shared dependency update policy. Updates are listed on each repository's dependency dashboard and open a pull request only when someone asks for them. Security fixes are exempt and open on their own, for the language ecosystems GitHub advisories and OSV cover. Docker tags and Helm charts have no advisory feed in either source, so a security fix for an image or a chart arrives as an ordinary dashboard entry and depends on someone reviewing that dashboard. Every Node.js runtime release is also exempt and arrives as one pull request per repository, so a Node security release or end of life never waits on a dashboard. npm lockfile updates rewrite tarball URLs to the configured registry's host, because npm 12 refuses tarballs from any other host, and keep each repository's own .npmrc.", + "description": "Datum's shared dependency update policy. Updates are listed on each repository's dependency dashboard and open a pull request only when someone asks for them. Security fixes are exempt and open on their own, for the language ecosystems GitHub advisories and OSV cover. Docker tags and Helm charts have no advisory feed in either source, so a security fix for an image or a chart arrives as an ordinary dashboard entry and depends on someone reviewing that dashboard. Every Node.js runtime release is also exempt and arrives as one pull request per repository, so a Node security release or end of life never waits on a dashboard. npm lockfile updates rewrite tarball URLs to the configured registry's host, because npm 12 refuses tarballs from any other host, and allow tarball URLs during that step only, because npm 12 still refuses a registry tarball it must unpack to read bundled dependencies, such as the optional WebAssembly build Tailwind 4 pulls in (npm/cli#9800). Each repository keeps its own .npmrc, so installs in CI keep npm 12's default refusal.", "extends": [ "config:recommended" ], "dependencyDashboardApproval": true, "osvVulnerabilityAlerts": true, - "npmrc": "replace-registry-host=always", + "npmrc": "replace-registry-host=always\nallow-remote=all", "npmrcMerge": true, "addLabels": ["renovate"], "vulnerabilityAlerts": {