Fix broken pnpm-lock.yaml#37757
Conversation
| optionalDependencies: | ||
| '@esbuild/aix-ppc64': 0.27.4 | ||
| '@esbuild/android-arm': 0.27.4 | ||
| '@esbuild/android-arm64': 0.27.4 | ||
| '@esbuild/android-x64': 0.27.4 | ||
| '@esbuild/darwin-arm64': 0.27.4 | ||
| '@esbuild/darwin-x64': 0.27.4 | ||
| '@esbuild/freebsd-arm64': 0.27.4 | ||
| '@esbuild/freebsd-x64': 0.27.4 | ||
| '@esbuild/linux-arm': 0.27.4 | ||
| '@esbuild/linux-arm64': 0.27.4 | ||
| '@esbuild/linux-ia32': 0.27.4 | ||
| '@esbuild/linux-loong64': 0.27.4 | ||
| '@esbuild/linux-mips64el': 0.27.4 | ||
| '@esbuild/linux-ppc64': 0.27.4 | ||
| '@esbuild/linux-riscv64': 0.27.4 | ||
| '@esbuild/linux-s390x': 0.27.4 | ||
| '@esbuild/linux-x64': 0.27.4 | ||
| '@esbuild/netbsd-arm64': 0.27.4 | ||
| '@esbuild/netbsd-x64': 0.27.4 | ||
| '@esbuild/openbsd-arm64': 0.27.4 | ||
| '@esbuild/openbsd-x64': 0.27.4 | ||
| '@esbuild/openharmony-arm64': 0.27.4 | ||
| '@esbuild/sunos-x64': 0.27.4 | ||
| '@esbuild/win32-arm64': 0.27.4 | ||
| '@esbuild/win32-ia32': 0.27.4 | ||
| '@esbuild/win32-x64': 0.27.4 |
There was a problem hiding this comment.
esbuild@0.27.4 now only lists a small subset of its platform-specific optional dependencies in the lockfile (e.g., missing @esbuild/darwin-arm64, @esbuild/linux-arm64, etc.). This will likely cause pnpm install --frozen-lockfile to fail or force lockfile changes when installing on other OS/CPU combinations. Regenerate the lockfile in an environment/config that does not prune optional dependencies by architecture (e.g., ensure no global supportedArchitectures/platform filters are applied) so all supported @esbuild/* entries are present.
| turbo@2.8.19: | ||
| optionalDependencies: | ||
| '@turbo/darwin-64': 2.8.19 | ||
| '@turbo/darwin-arm64': 2.8.19 | ||
| '@turbo/linux-64': 2.8.19 | ||
| '@turbo/linux-arm64': 2.8.19 | ||
| '@turbo/windows-64': 2.8.19 |
There was a problem hiding this comment.
turbo@2.8.19 optionalDependencies are missing the arm64 variants in the lockfile (e.g., @turbo/darwin-arm64, @turbo/linux-arm64, @turbo/windows-arm64). If developers/CI run pnpm install --frozen-lockfile on those architectures, the install may fail or rewrite the lockfile. Regenerate the lockfile without architecture pruning so all Turbo platform packages are included.
| vitest: | ||
| specifier: catalog:testing | ||
| version: 4.0.18(@opentelemetry/api@1.9.0)(@types/node@20.19.37)(@vitest/browser-playwright@4.0.18)(tsx@4.21.0)(yaml@2.8.2) | ||
| version: 4.1.0(@opentelemetry/api@1.9.0)(@types/node@20.19.37)(@vitest/browser-playwright@4.1.0)(vite@7.3.1(@types/node@20.19.37)(tsx@4.21.0)(yaml@2.8.2)) |
There was a problem hiding this comment.
The PR description suggests this is only a lockfile repair, but this hunk also updates the testing toolchain versions (e.g., vitest / @vitest/* to 4.1.0). If the intent is strictly “repair without upgrading”, regenerate the lockfile in a way that preserves the previous resolved versions; otherwise please explicitly call out the Vitest upgrade in the PR description to avoid surprise behavior changes in CI/tests.
|
Closing in favor of #37758 which doesn't have the esbuild changes |
Suspect this was broken by #37740
Ran
pnpm installlocally to repair