`run-as-installed.mjs` now checks, before it runs the command, that every
`@tanstack/*` dependency of the project resolves to a package inside the
`pnpm deploy` copy. If a change to pnpm's settings or to `deploy` left a
link into `packages/*`, the run would test the linked workspace again and
still pass. `run-as-installed.md` says how the run is part of CI.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- With `tanstackStart()` in a config that Vitest loads, test files are
compiled as the app's code is: for the client in browser mode, jsdom
and happy-dom, for the server in Node. A test run sets up no dev
server, preview server or build. A project needs no router entry and
no routes. The route tree is generated once, and route files are never
written.
- `mockServerFn` and `resetServerFnMocks` in `<framework>-start/testing`:
in a client test a server function call goes to a mock that is typed
from the function, in place of a request.
- `runInRequest`, `mockMiddleware` and `runMiddleware` in
`<framework>-start/testing/server`: a server test runs server functions
and middleware for a request it describes.
- Mocks end with the test that registered them. The plugin adds a setup
file to every Vitest project for that.
- In a test run the server finds a server function by its id alone.
Vitest serves compiled modules from its cache from the second run on,
so the compiler has no record of them.
- In a test run Start names its packages in `resolve.noExternal` with
regular expressions. Vitest's translation of the wildcards does not
match a `-`, so jsdom and Node tests of an installed project ran
`@tanstack/start-client-core` uncompiled.
- `@tanstack/react-start` pre-bundles `@tanstack/react-store` by a path
that also resolves from a project that depends on Start only.
- `scripts/e2e/run-as-installed.mjs` runs an e2e project from a
`pnpm deploy` copy, where `@tanstack/*` are in `node_modules` as in a
user's project.
- `e2e/react-start/vitest-library` and `e2e/react-start/vitest-app` run
their tests with an empty Vitest cache, from the warm cache and as an
installed project.
- Docs: `docs/start/framework/react/guide/testing.md`.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* chore(pnpm): upgrade to pnpm 12
* ci: use native pnpm 12 bootstrap for compiler jobs
* fix(benchmarks): invoke the Nx CLI directly
* refactor(benchmarks): run Nx through pnpm exec
The measurement target was named `build`, so `test:pr`/`test:ci` and
`build:all` picked it up via `--targets=...,build`. Its cache entry was
never reused: the Bundle Size workflow runs with NX_NO_CLOUD and
--skipRemoteCache. Rename it to `measure` (with explicit `cache: true`,
previously inherited from the `build` target default).
Since dependency-only changes no longer reach this target through
`nx affected`, add `.nvmrc`, `package.json` and `pnpm-lock.yaml` to the
Bundle Size workflow path filters so toolchain bumps are still measured.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* perf(benchmarks): compress bundle-size outputs once
* add link to readme in skill
* ci: apply automated fixes
* fix(benchmarks): persist timing flag in measurement command
---------
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* add sharding
* fix dependnancy
* fix playwright shard port reuse
* full bust
* throw more runners into this run
* try to throw money at it and see the effect
* tune