Skip to content

ci(e2e): Run E2E tests with pnpm 12 - #25334

Merged
s1gr1d merged 10 commits into
developfrom
sig/e2e-pnpm-12
Oct 15, 2026
Merged

s1gr1d merged 10 commits into
developfrom
sig/e2e-pnpm-12

Conversation

@s1gr1d

@s1gr1d s1gr1d commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Moves the E2E tests from pnpm 9 to pnpm 12. Volta still manages node.

  • Every app has a pnpm-workspace.yaml. pnpm 11+ reads its settings only from this file.
    • allowBuilds: pnpm 11+ fails the install on build scripts that are not listed. false is only for scripts that just print a message.
    • minimumReleaseAge: 0: by default, pnpm 11+ installs only releases that are at least 24 hours old, and falls back to older versions. The apps test against the newest releases, so the E2E runner fails if an app does not set it.
  • Updated to @electron/rebuild ^4.2.1. Older versions depend on @electron/node-gyp from git, and pnpm 11+ blocks git dependencies of dependencies.
  • Ignored overrides fixed. The bundler-plugin fixtures had overrides in package.json#pnpm, and some apps used package.json#resolutions. pnpm 11+ ignores both without an error. The E2E runner now fails if an app still uses them.
  • Test app fixes for pnpm 12.
    • The Next.js tests and build assertions read the installed version from next/package.json. pnpm add next@15 now saves ^15.x.y, and the old version checks did not work with the ^.
    • The tanstackstart apps use "nitro": "^3.0.0", because pnpm 12 resolved latest || * to the placeholder nitro@0.0.0. This installs the same nitro@3.0.0 as pnpm 9. A follow-up moves them to the nitro beta, which needs Vite 8.
    • 7 apps no longer run npx playwright install in test:build. CI already installs the app's Playwright version, and the second install ran at the same time and failed.

Why pnpm is a root dev dependency

pnpm switches to the version in a packageManager field, but a pnpm must already be installed to do that. Yarn installs that first pnpm as a dev dependency, because Volta can't run pnpm 12 and is unmaintained. The pnpm package is a native binary, so it does not depend on the node version that an app pins. yarn.lock pins the version, so local runs and CI use the same pnpm. Contributors need no extra setup, and CI caches pnpm with node_modules.

Rejected alternatives:

  • pnpm/action-setup alone: it only installs pnpm in CI. Contributors would have to install pnpm themselves, and their version could differ from CI.
  • Corepack: it is deprecated, and Node 25 no longer includes it.
  • mise: no getsentry JS repo uses it, and contributors would need one more tool (alongside Volta).

⚠️ @JPeer264 When the repo moves from Yarn to pnpm, remove the dev dependency and set packageManager in the root package.json. A test app can still pin another pnpm version (10.30 or newer, which reads allowBuilds) with its own packageManager field.

Volta cannot run pnpm 12, so pnpm is now a root devDependency. Volta only
pins node per app. pnpm 11+ reads settings only from pnpm-workspace.yaml and
blocks unlisted build scripts, so each app now has a pnpm-workspace.yaml with
allowBuilds and minimumReleaseAge: 0.
@s1gr1d
s1gr1d marked this pull request as ready for review October 14, 2026 10:26
@s1gr1d
s1gr1d requested review from JPeer264 and mydea October 14, 2026 11:17
Comment thread dev-packages/bundler-plugin-integration-tests/fixtures/esbuild/package.json Outdated
"typescript": "~5.8.3",
"vite": "^7.3.2"
},
"volta": {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not directly related to this test, but we should actually replace these with a reference to the workspace volta config.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I may open a PR to update this everywhere)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mydea

mydea commented Oct 14, 2026

Copy link
Copy Markdown
Member

Semi related, opened #25369 to actually update volta config in e2e test apps to better align with the fact we are using node 24 anyhow now by default!

Comment thread dev-packages/e2e-tests/test-applications/aws-serverless-layer/package.json Outdated
# Conflicts:
#	dev-packages/e2e-tests/test-applications/browser-bfcache/package.json
#	dev-packages/e2e-tests/test-applications/browser-mfe-vite/package.json
#	dev-packages/e2e-tests/test-applications/browser-webworker-vite/package.json
#	dev-packages/e2e-tests/test-applications/remix-v3/package.json
@JPeer264
JPeer264 added this pull request to stack #25387 October 15, 2026 08:47
# Conflicts:
#	dev-packages/bundler-plugin-integration-tests/fixtures/esbuild/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/rolldown/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/rollup3/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/rollup4/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/vite4/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/vite6/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/vite7/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/vite8/package.json
#	dev-packages/bundler-plugin-integration-tests/fixtures/webpack5/package.json

@JPeer264 JPeer264 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just added nits mostly

Comment thread .agents/skills/e2e/SKILL.md Outdated
- **Packed tarballs missing**: Run `yarn build:tarball` at the repo root, then `yarn test:prepare` in `dev-packages/e2e-tests`
- **Build failures**: Fix build errors before running tests
- **pnpm errors such as `packages field missing or empty`**: The app needs the pnpm version in its `volta.pnpm`. Run with Volta, which installs that version
- **`ERR_PNPM_IGNORED_BUILDS`**: A dependency has a build script that the app's `allowBuilds` does not list. Add it to the app's `pnpm-workspace.yaml`: `true` if the app needs the script, `false` if the script only prints a message

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

l: Theoretically pnpm approve-builds is adding it - maybe worth to add this here

Comment thread .github/actions/install-pnpm/action.yml Outdated
steps:
- name: Resolve pnpm version
id: pnpm-version
# The devDependency is the one pnpm version for CI and local runs. An app that needs another version sets

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

super-l: It is weird that it is written devDependency and not "dev dependency" - maybe we can rename it to the latter. First I read it any thought that something is off 😅

Suggested change
# The devDependency is the one pnpm version for CI and local runs. An app that needs another version sets
# The dev dependency is the one pnpm version for CI and local runs. An app that needs another version sets

@@ -0,0 +1 @@
minimumReleaseAge: 0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q/l: Couldn't we make one more global pnpm-workspace.yaml in the e2e test root and copy it over into each directory? Theoretically we don't treat each folder as own workspace, but we potentially forget to set minimumRelaseAge: 0 on new tests.

If we keep it though, we should add a bugbot rule that this is set as a minimum on new e2e tests or make sure in our runners that this is set. wdyt?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll add a rule for that 👍

Comment thread dev-packages/e2e-tests/test-applications/hydrogen-react-router-7/package.json Outdated
"react": "^19.2.0",
"react-dom": "^19.2.0",
"nitro": "latest || *",
"nitro": "^3.0.0",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q: Is that change necessary in this PR? Or was it required to be changed

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, listed in the PR description:

The tanstackstart apps use "nitro": "^3.0.0", because pnpm 12 resolved latest || * to the placeholder nitro@0.0.0. This installs the same nitro@3.0.0 as pnpm 9. A follow-up moves them to the nitro beta, which needs Vite 8.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for confirming. Sorry I forgot the PR description after scrolling through all the changes 😅

"react": "^19.2.0",
"react-dom": "^19.2.0",
"nitro": "latest || *",
"nitro": "^3.0.0",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread dev-packages/e2e-tests/README.md Outdated
@s1gr1d
s1gr1d merged commit 1c5303c into develop Oct 15, 2026
1096 of 1103 checks passed
@s1gr1d
s1gr1d deleted the sig/e2e-pnpm-12 branch October 15, 2026 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants