fix(examples): install from the 0.23.0 runner and engine releases

Merged
IJ
3d ago
+20-20

What and why

  • The examples pin e2e ^0.22.0 with @e2e-dev/web ^0.15.4 or @e2e-dev/mobile ^0.12.5. npm resolves the engine patches 0.15.5 and 0.12.6, whose e2e peer is >=0.22.1. No stable 0.22.1 exists, and ^0.22.0 excludes 0.23.0, so a fresh npm install fails with ERESOLVE.
  • Bump to the released set: e2e ^0.23.0, web ^0.15.5, mobile ^0.12.6.
  • Changed: with-vite, with-next, with-astro, with-angular, with-compose, with-flutter, with-kotlin-multiplatform, with-maui.
  • with-expo was already bumped on main by #1705 and is unchanged here.
  • with-swiftui already used the new set and is unchanged.
  • This is the consumer-side unblock. The release-check fix for the root cause is #1657, implemented by #1661, not this PR.

Issue

Refs #1657

Verified

Ran it locally: yes

  • npm install --dry-run in all 9 changed examples: every tree resolves.
  • Web examples, normal npm install plus the suite:
ExampleInstallSuite
with-vitepass5 passed: 3 deterministic, 2 agent on a temporary opencodeConsole('go/deepseek-v4.1-flash') model
with-nextpass3 passed, 2 agent skipped
with-astropass3 passed, 2 agent skipped
with-angularpass3 passed, 2 agent skipped
with-expo (web)pass3 passed, 2 agent skipped; already on the new set on main
  • Native examples (with-compose, with-flutter, with-kotlin-multiplatform, with-maui): npm install --ignore-scripts passes. Their suites need an iOS simulator or Android emulator, so they were skipped for now.

examples/with-vite on main fails at npm install; on this branch it installs and all 5 tests pass.

Checklist

  • No changeset: examples are private, outside the pnpm workspace, and publish nothing.
  • No breaking change and no public contract change; only devDependency ranges.
  • Docs: the four web example READMEs this PR changes record the 0.23.0 check. with-expo is already current on main. Native READMEs are unchanged because their suites were not run.