From 3d172e608a38ea4694cbda898da32a30ca14a364 Mon Sep 17 00:00:00 2001 From: Ian Pascoe Date: Fri, 13 Nov 2026 08:37:53 -0500 Subject: [PATCH 1/2] build: pin the type-aware lint backend in vite.config.ts and configure Pi for the repo Vite+ sets OXLINT_TSGOLINT_PATH only when it is unset, so agents and worktrees that inherited another checkout's (or a stale) value linted on another tsrs or failed. The root vite.config.ts now assigns it to the tsrs-lint shim. .pi/settings.json runs Pi's formatter and language servers on the project's vp and Effect-patched tsrs. --- .pi/settings.json | 57 ++++++++++++++++++++++++++++ docs/adr/0055-vite-plus-and-pnpm.md | 3 +- docs/development/dependencies.md | 2 +- tools/tsrs-lint-shim/bin/tsgolint.js | 7 ++-- vite.config.ts | 9 +++++ 5 files changed, 73 insertions(+), 5 deletions(-) create mode 100644 .pi/settings.json diff --git a/.pi/settings.json b/.pi/settings.json new file mode 100644 index 00000000..faf99af9 --- /dev/null +++ b/.pi/settings.json @@ -0,0 +1,57 @@ +{ + "formatter": { + "formatters": { + "oxfmt": { + "command": "pnpm", + "args": ["exec", "vp", "fmt", "--no-error-on-unmatched-pattern", "$FILE"], + "files": { + "extensions": [ + ".js", + ".jsx", + ".ts", + ".tsx", + ".mjs", + ".cjs", + ".mts", + ".cts", + ".json", + ".jsonc", + ".md", + ".yml", + ".yaml", + ".css" + ] + }, + "rootMarkers": ["pnpm-workspace.yaml"], + "requireRootMarker": true + } + } + }, + "lsp": { + "servers": { + "typescript": { + "command": "pnpm", + "args": ["exec", "effect-tsgo", "tsrs", "--lsp", "--stdio"], + "languages": [ + { "extensions": [".ts", ".mts", ".cts"], "languageId": "typescript" }, + { "extensions": [".tsx"], "languageId": "typescriptreact" } + ], + "rootMarkers": ["tsconfig.json"], + "workspaceRootMarkers": ["pnpm-workspace.yaml"], + "requireRootMarker": true + }, + "oxlint": { + "command": "pnpm", + "args": ["exec", "vp", "lint", "--lsp"], + "languages": [ + { "extensions": [".js", ".mjs", ".cjs"], "languageId": "javascript" }, + { "extensions": [".jsx"], "languageId": "javascriptreact" }, + { "extensions": [".ts", ".mts", ".cts"], "languageId": "typescript" }, + { "extensions": [".tsx"], "languageId": "typescriptreact" } + ], + "rootMarkers": ["pnpm-workspace.yaml"], + "requireRootMarker": true + } + } + } +} diff --git a/docs/adr/0055-vite-plus-and-pnpm.md b/docs/adr/0055-vite-plus-and-pnpm.md index c7479ac5..9c3b404b 100644 --- a/docs/adr/0055-vite-plus-and-pnpm.md +++ b/docs/adr/0055-vite-plus-and-pnpm.md @@ -21,7 +21,8 @@ Measured on an 8-core Apple Silicon laptop (2026-11-12), warm caches: ## Consequences -- The type-aware lint runs on tsrs's own linter (`tsrs-lint`, `tsrs --lint`, since tsrs 0.21: tsgolint's headless protocol and its 61 type-aware rules), which replaces tsrslint, its predecessor outside tsrs. Vite+ sets `OXLINT_TSGOLINT_PATH` to the `bin/tsgolint` of its own `oxlint-tsgolint` and ignores `node_modules/.bin`, so `scripts/link-tsrslint.sh` is gone, and a pnpm override makes `oxlint-tsgolint` the repo's `tools/tsrs-lint-shim`, whose `bin/tsgolint.js` loads the root `tsrs` package's `tsrs-lint`. It rests on where Vite+ looks for its backend (docs/development/dependencies.md says what to check on an upgrade). The shim has no `package.json`, or `effect-tsgo patch` finds it as Vite+'s `oxlint-tsgolint` and fails `prepare` looking for tsgolint's platform binary. The `tsrs` package is the linter only: `effect-tsgo tsrs` typechecks with the Effect-patched tsrs that `@effect/tsgo` ships. It goes once `effect-tsgo --tsrs-lint vp lint` (`@effect/tsgo` 0.68 and later: Vite+'s lint on the Effect-patched tsrs, with the Effect rules, and no shim) can run, which needs oxlint 1.91 or later, so a Vite+ past 1.4.0 (`Versions`). The shim does not run on Windows, where Vite+ looks for `tsgolint.exe` or `tsgolint.cmd` in `.bin`, not the `.js` the shim is; tsrs itself ships for macOS, Linux (glibc and musl) and Windows. +- The type-aware lint runs on tsrs's own linter (`tsrs-lint`, `tsrs --lint`, since tsrs 0.21: tsgolint's headless protocol and its 61 type-aware rules), which replaces tsrslint, its predecessor outside tsrs. Vite+ sets `OXLINT_TSGOLINT_PATH` to the `bin/tsgolint` of its own `oxlint-tsgolint` and ignores `node_modules/.bin`, so `scripts/link-tsrslint.sh` is gone, and a pnpm override makes `oxlint-tsgolint` the repo's `tools/tsrs-lint-shim`, whose `bin/tsgolint.js` loads the root `tsrs` package's `tsrs-lint`. Vite+ fills that variable in only when it is unset, so the root `vite.config.ts` assigns it to the shim itself: a process that inherited another checkout's value, as Pi's agents and the language servers they start do, linted on that checkout's tsrs, and a stale value failed the lint. Every Vite+ entry point that lints (`vp lint`, `vp check`, `vp staged`, `vp lint --lsp`) loads that config first. It rests on where Vite+ looks for its backend (docs/development/dependencies.md says what to check on an upgrade). The shim has no `package.json`, or `effect-tsgo patch` finds it as Vite+'s `oxlint-tsgolint` and fails `prepare` looking for tsgolint's platform binary. The `tsrs` package is the linter only: `effect-tsgo tsrs` typechecks with the Effect-patched tsrs that `@effect/tsgo` ships. It goes once `effect-tsgo --tsrs-lint vp lint` (`@effect/tsgo` 0.68 and later: Vite+'s lint on the Effect-patched tsrs, with the Effect rules, and no shim) can run, which needs oxlint 1.91 or later, so a Vite+ past 1.4.0 (`Versions`). The shim does not run on Windows, where Vite+ looks for `tsgolint.exe` or `tsgolint.cmd` in `.bin`, not the `.js` the shim is; tsrs itself ships for macOS, Linux (glibc and musl) and Windows. +- Pi's agents format with `pnpm exec vp fmt` and run two language servers from `.pi/settings.json`: `pnpm exec vp lint --lsp` (this lint, rooted at `pnpm-workspace.yaml`) and `pnpm exec effect-tsgo tsrs --lsp --stdio` (the typecheck's Effect-patched tsrs, one per package `tsconfig.json`). They replace the owner's global definitions, which look for `.oxlintrc.json` and `.oxfmtrc.json` and run a tsrs without the Effect diagnostics. - Run the project's own `vp`: `pnpm exec vp`, the root scripts, or the standalone global CLI from vite.plus, which hands a command to the project's copy. mise's `npm:vite-plus` is a second copy of the whole toolchain. - Turborepo's CI pruning is gone; the Vite Task cache is experimental in CI (Vite+'s docs say so) and is bounded by size instead. - On macOS, Vite Task runs a cached task's system coreutils as uutils' to record what it reads. The tests that probe the host for GNU coreutils check `--version` for `(GNU coreutils)`, and `@cloudpid/sandbox-image`'s `test` is uncached, since its memory-guard tests fail under uutils. Linux is unaffected. diff --git a/docs/development/dependencies.md b/docs/development/dependencies.md index e981ae86..f4583f95 100644 --- a/docs/development/dependencies.md +++ b/docs/development/dependencies.md @@ -6,7 +6,7 @@ Some dependencies carry a patch (`patches/`) or an exact pin. When upgrading one | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `@cloudflare/vitest-plugin` | `patches/@cloudflare__vitest-plugin@1.8.0.patch` | Keeps the module snapshot it sends a reused worker under workerd's 32 MiB WebSocket message limit, past which the worker dies with `1009 Message is too large` ([cloudflare/workers-sdk#16349](https://github.com/cloudflare/workers-sdk/issues/16349)). Drop it once #16349 is fixed. | | `vite-plus`, `vitest` | exact `1.4.0` (`vite-plus`) in the root `package.json` and `apps/web`; exact `5.0.5` (`vitest`) at the root and in the packages whose test plugins peer it; the `vite` and `vitest` `overrides` in `pnpm-workspace.yaml` (`@voidzero-dev/vite-plus-core@1.4.0`, `5.0.5`) | Vite+ bundles its own Vitest (1.4.0 bundles 5.0.5; 1.5 and later bundle 5.1), so `vite-plus`, the `vite` override and `vitest` move together. Vitest is held below 5.1: under 5.1.0 the workerd pool delays a timer a Durable Object request sets (`setImmediate`, `setTimeout(0)`) until a later request to an object awaits a real timer, so an Effect fiber forked in a request (Effect's scheduler starts it with `setImmediate`) starts late: a Session reports itself idle only at its next request, and `apps/server/src/session/admission.workerd.test.ts` ("Stop waits for it"), `host.workerd.test.ts` and `import.workerd.test.ts` fail. Bisected on its own (5.0.5 with the same workerd, `@cloudflare/vitest-plugin`, Effect and pi-durable delivers them at once); deployed workerd is unaffected. Still failing on 2026-11-13 with `vite-plus` 1.6.0, Vitest 5.1.0, `@cloudflare/vitest-plugin` 1.8.0 and workerd 1.20261110 (the same three files). Before lifting it, check that a `setImmediate` set in a `runInDurableObject` callback runs before the next no-op `runInDurableObject` returns, and rerun those three files. | -| `tsrs`, `oxlint-tsgolint` | exact `0.25.0-ts7.1.0-beta` (`tsrs`) in the root `package.json`; `oxlint-tsgolint` overridden to `link:./tools/tsrs-lint-shim` in `pnpm-workspace.yaml` | Vite+'s type-aware lint backend is tsrs's own linter, `tsrs-lint`, through the shim (`tools/tsrs-lint-shim/bin/tsgolint.js`; [ADR-0055](../adr/0055-vite-plus-and-pnpm.md) → Consequences). This `tsrs` is the linter only; the typecheck is `effect-tsgo tsrs`, the tsrs that `@effect/tsgo` ships, whatever this pin says. When upgrading `vite-plus` or `tsrs`, check that `pnpm exec vp lint` on a file with a type error and a floating promise still reports both (`typescript(TS2322)`, `no-floating-promises`): a Vite+ that looks for its backend elsewhere fails with `Error running tsgolint`, and a tsrs that speaks a newer tsgolint protocol than Vite+'s oxlint may not be understood. It does not run on Windows, where Vite+ looks for `tsgolint.exe` or `.cmd` instead. Drop the override, the shim and `tsrs` once `effect-tsgo --tsrs-lint vp lint` runs (`@effect/tsgo` 0.68 and later, with oxlint 1.91 or later). | +| `tsrs`, `oxlint-tsgolint` | exact `0.25.0-ts7.1.0-beta` (`tsrs`) in the root `package.json`; `oxlint-tsgolint` overridden to `link:./tools/tsrs-lint-shim` in `pnpm-workspace.yaml` | Vite+'s type-aware lint backend is tsrs's own linter, `tsrs-lint`, through the shim (`tools/tsrs-lint-shim/bin/tsgolint.js`; [ADR-0055](../adr/0055-vite-plus-and-pnpm.md) → Consequences). This `tsrs` is the linter only; the typecheck is `effect-tsgo tsrs`, the tsrs that `@effect/tsgo` ships, whatever this pin says. When upgrading `vite-plus` or `tsrs`, check that `pnpm exec vp lint` on a file with a type error and a floating promise still reports both (`typescript(TS2322)`, `no-floating-promises`), also with `OXLINT_TSGOLINT_PATH` set to a missing file (the root `vite.config.ts` must replace an inherited value): a Vite+ that looks for its backend elsewhere fails with `Error running tsgolint`, and a tsrs that speaks a newer tsgolint protocol than Vite+'s oxlint may not be understood. It does not run on Windows, where Vite+ looks for `tsgolint.exe` or `.cmd` instead. Drop the override, the shim and `tsrs` once `effect-tsgo --tsrs-lint vp lint` runs (`@effect/tsgo` 0.68 and later, with oxlint 1.91 or later). | | `ws` | exact `8.22.1`, an `overrides` entry in `pnpm-workspace.yaml` | One `ws` for every package: `@earendil-works/chord` pins `8.21.0` and the rest resolve 8.22, and each `ws` is a peer variant of `alchemy`, whose two copies then fail `infra`'s typecheck (a union of two `AlchemyContext`s). Drop it once chord allows 8.22, or move it with the newest `ws` chord allows. | | `@cloudflare/computer` | `patches/@cloudflare__computer@0.11.1.patch` | Adds `Workspace.remount()`, which `updateSkills` runs: computer checks a mount's version only at a Workspace's first index ([`../architecture/workspace.md`](../architecture/workspace.md) → _The Skill set_). Drop it once computer can index a mount again; rerun `apps/server/src/workspace/skills.workerd.test.ts` either way. Also update the `bash` routing lists if the Worker Shell changed ([`workers.md`](workers.md) → _The Workspace DO_). | | `@cloudflare/computer`, computerd | read for the file-change signal | The file-change signal ([`../architecture/container.md`](../architecture/container.md) → _File-change signals_) reads computer's change-log tables (`apps/server/src/workspace/change-log.ts`) and span names (`notify.ts`), and needs computerd's `setxattr` on its mount to stay a no-op the kernel reports. When upgrading either, rerun `src/workspace/notify.workerd.test.ts` and `notify.test.ts`, and recheck by hand as that section's _Limits_ says. | diff --git a/tools/tsrs-lint-shim/bin/tsgolint.js b/tools/tsrs-lint-shim/bin/tsgolint.js index b38d8a97..ce79396b 100755 --- a/tools/tsrs-lint-shim/bin/tsgolint.js +++ b/tools/tsrs-lint-shim/bin/tsgolint.js @@ -1,9 +1,10 @@ #!/usr/bin/env node // Vite+'s type-aware lint backend, run as tsrs's own linter (`tsrs-lint`, tsrs's port of tsgolint's headless mode and // rules) instead of tsgolint (docs/adr/0055-vite-plus-and-pnpm.md → Consequences). `vp lint` and `vp check` run the -// `bin/tsgolint` of the `oxlint-tsgolint` they resolve, from the working directory first and then from `vite-plus`, and -// set `OXLINT_TSGOLINT_PATH` to it themselves, so `pnpm-workspace.yaml`'s overrides make this directory that package (no -// workspace package declares `oxlint-tsgolint`, which would take its place). It has no `package.json` on purpose: +// `bin/tsgolint` of the `oxlint-tsgolint` they resolve, from the working directory first and then from `vite-plus`, so +// `pnpm-workspace.yaml`'s overrides make this directory that package (no workspace package declares `oxlint-tsgolint`, +// which would take its place). They set `OXLINT_TSGOLINT_PATH` to it only when it is unset, so the root +// `vite.config.ts` assigns it to this file first. It has no `package.json` on purpose: // `effect-tsgo patch` (the root `prepare`) looks for Vite+'s `oxlint-tsgolint` by its `package.json`, and would then fail // the install looking for tsgolint's platform binary, which this replaces. import { readFileSync } from "node:fs"; diff --git a/vite.config.ts b/vite.config.ts index fde9345b..8eeaf63d 100644 --- a/vite.config.ts +++ b/vite.config.ts @@ -4,6 +4,15 @@ import { fileURLToPath } from "node:url"; import { defineConfig } from "vite-plus"; +// oxlint's type-aware backend: tsrs's linter, through the shim `pnpm-workspace.yaml` installs as `oxlint-tsgolint` +// (tools/tsrs-lint-shim/bin/tsgolint.js). Vite+ fills the variable in only when it is unset, so an agent or a worktree +// that inherited another checkout's value, or a stale one, would lint with that tsrs or fail. Assigned here, it holds +// for every Vite+ entry point that lints: `vp lint`, `vp check`, `vp staged` and `vp lint --lsp` +// (docs/adr/0055-vite-plus-and-pnpm.md → Consequences). +process.env.OXLINT_TSGOLINT_PATH = fileURLToPath( + new URL("tools/tsrs-lint-shim/bin/tsgolint.js", import.meta.url), +); + /** Directories of other tools and agents, and the reference repositories (`.repos/`), which nothing here formats or lints. */ const ignorePatterns = [ ".agent/**", From 510bf5614084db0801e3f433a168f7de6efeff90 Mon Sep 17 00:00:00 2001 From: Ian Pascoe Date: Fri, 13 Nov 2026 08:39:33 -0500 Subject: [PATCH 2/2] docs: say why the tsrs-lint shim cannot run on Windows --- docs/adr/0055-vite-plus-and-pnpm.md | 2 +- docs/development/dependencies.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/adr/0055-vite-plus-and-pnpm.md b/docs/adr/0055-vite-plus-and-pnpm.md index 9c3b404b..2a4a46cd 100644 --- a/docs/adr/0055-vite-plus-and-pnpm.md +++ b/docs/adr/0055-vite-plus-and-pnpm.md @@ -21,7 +21,7 @@ Measured on an 8-core Apple Silicon laptop (2026-11-12), warm caches: ## Consequences -- The type-aware lint runs on tsrs's own linter (`tsrs-lint`, `tsrs --lint`, since tsrs 0.21: tsgolint's headless protocol and its 61 type-aware rules), which replaces tsrslint, its predecessor outside tsrs. Vite+ sets `OXLINT_TSGOLINT_PATH` to the `bin/tsgolint` of its own `oxlint-tsgolint` and ignores `node_modules/.bin`, so `scripts/link-tsrslint.sh` is gone, and a pnpm override makes `oxlint-tsgolint` the repo's `tools/tsrs-lint-shim`, whose `bin/tsgolint.js` loads the root `tsrs` package's `tsrs-lint`. Vite+ fills that variable in only when it is unset, so the root `vite.config.ts` assigns it to the shim itself: a process that inherited another checkout's value, as Pi's agents and the language servers they start do, linted on that checkout's tsrs, and a stale value failed the lint. Every Vite+ entry point that lints (`vp lint`, `vp check`, `vp staged`, `vp lint --lsp`) loads that config first. It rests on where Vite+ looks for its backend (docs/development/dependencies.md says what to check on an upgrade). The shim has no `package.json`, or `effect-tsgo patch` finds it as Vite+'s `oxlint-tsgolint` and fails `prepare` looking for tsgolint's platform binary. The `tsrs` package is the linter only: `effect-tsgo tsrs` typechecks with the Effect-patched tsrs that `@effect/tsgo` ships. It goes once `effect-tsgo --tsrs-lint vp lint` (`@effect/tsgo` 0.68 and later: Vite+'s lint on the Effect-patched tsrs, with the Effect rules, and no shim) can run, which needs oxlint 1.91 or later, so a Vite+ past 1.4.0 (`Versions`). The shim does not run on Windows, where Vite+ looks for `tsgolint.exe` or `tsgolint.cmd` in `.bin`, not the `.js` the shim is; tsrs itself ships for macOS, Linux (glibc and musl) and Windows. +- The type-aware lint runs on tsrs's own linter (`tsrs-lint`, `tsrs --lint`, since tsrs 0.21: tsgolint's headless protocol and its 61 type-aware rules), which replaces tsrslint, its predecessor outside tsrs. Vite+ sets `OXLINT_TSGOLINT_PATH` to the `bin/tsgolint` of its own `oxlint-tsgolint` and ignores `node_modules/.bin`, so `scripts/link-tsrslint.sh` is gone, and a pnpm override makes `oxlint-tsgolint` the repo's `tools/tsrs-lint-shim`, whose `bin/tsgolint.js` loads the root `tsrs` package's `tsrs-lint`. Vite+ fills that variable in only when it is unset, so the root `vite.config.ts` assigns it to the shim itself: a process that inherited another checkout's value, as Pi's agents and the language servers they start do, linted on that checkout's tsrs, and a stale value failed the lint. Every Vite+ entry point that lints (`vp lint`, `vp check`, `vp staged`, `vp lint --lsp`) loads that config first. It rests on where Vite+ looks for its backend (docs/development/dependencies.md says what to check on an upgrade). The shim has no `package.json`, or `effect-tsgo patch` finds it as Vite+'s `oxlint-tsgolint` and fails `prepare` looking for tsgolint's platform binary. The `tsrs` package is the linter only: `effect-tsgo tsrs` typechecks with the Effect-patched tsrs that `@effect/tsgo` ships. It goes once `effect-tsgo --tsrs-lint vp lint` (`@effect/tsgo` 0.68 and later: Vite+'s lint on the Effect-patched tsrs, with the Effect rules, and no shim) can run, which needs oxlint 1.91 or later, so a Vite+ past 1.4.0 (`Versions`). The shim does not run on Windows, where oxlint cannot start the `.js` the variable names (and Vite+ itself looks for `tsgolint.exe` or `tsgolint.cmd` in `.bin`); tsrs itself ships for macOS, Linux (glibc and musl) and Windows. - Pi's agents format with `pnpm exec vp fmt` and run two language servers from `.pi/settings.json`: `pnpm exec vp lint --lsp` (this lint, rooted at `pnpm-workspace.yaml`) and `pnpm exec effect-tsgo tsrs --lsp --stdio` (the typecheck's Effect-patched tsrs, one per package `tsconfig.json`). They replace the owner's global definitions, which look for `.oxlintrc.json` and `.oxfmtrc.json` and run a tsrs without the Effect diagnostics. - Run the project's own `vp`: `pnpm exec vp`, the root scripts, or the standalone global CLI from vite.plus, which hands a command to the project's copy. mise's `npm:vite-plus` is a second copy of the whole toolchain. - Turborepo's CI pruning is gone; the Vite Task cache is experimental in CI (Vite+'s docs say so) and is bounded by size instead. diff --git a/docs/development/dependencies.md b/docs/development/dependencies.md index f4583f95..8a127373 100644 --- a/docs/development/dependencies.md +++ b/docs/development/dependencies.md @@ -6,7 +6,7 @@ Some dependencies carry a patch (`patches/`) or an exact pin. When upgrading one | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `@cloudflare/vitest-plugin` | `patches/@cloudflare__vitest-plugin@1.8.0.patch` | Keeps the module snapshot it sends a reused worker under workerd's 32 MiB WebSocket message limit, past which the worker dies with `1009 Message is too large` ([cloudflare/workers-sdk#16349](https://github.com/cloudflare/workers-sdk/issues/16349)). Drop it once #16349 is fixed. | | `vite-plus`, `vitest` | exact `1.4.0` (`vite-plus`) in the root `package.json` and `apps/web`; exact `5.0.5` (`vitest`) at the root and in the packages whose test plugins peer it; the `vite` and `vitest` `overrides` in `pnpm-workspace.yaml` (`@voidzero-dev/vite-plus-core@1.4.0`, `5.0.5`) | Vite+ bundles its own Vitest (1.4.0 bundles 5.0.5; 1.5 and later bundle 5.1), so `vite-plus`, the `vite` override and `vitest` move together. Vitest is held below 5.1: under 5.1.0 the workerd pool delays a timer a Durable Object request sets (`setImmediate`, `setTimeout(0)`) until a later request to an object awaits a real timer, so an Effect fiber forked in a request (Effect's scheduler starts it with `setImmediate`) starts late: a Session reports itself idle only at its next request, and `apps/server/src/session/admission.workerd.test.ts` ("Stop waits for it"), `host.workerd.test.ts` and `import.workerd.test.ts` fail. Bisected on its own (5.0.5 with the same workerd, `@cloudflare/vitest-plugin`, Effect and pi-durable delivers them at once); deployed workerd is unaffected. Still failing on 2026-11-13 with `vite-plus` 1.6.0, Vitest 5.1.0, `@cloudflare/vitest-plugin` 1.8.0 and workerd 1.20261110 (the same three files). Before lifting it, check that a `setImmediate` set in a `runInDurableObject` callback runs before the next no-op `runInDurableObject` returns, and rerun those three files. | -| `tsrs`, `oxlint-tsgolint` | exact `0.25.0-ts7.1.0-beta` (`tsrs`) in the root `package.json`; `oxlint-tsgolint` overridden to `link:./tools/tsrs-lint-shim` in `pnpm-workspace.yaml` | Vite+'s type-aware lint backend is tsrs's own linter, `tsrs-lint`, through the shim (`tools/tsrs-lint-shim/bin/tsgolint.js`; [ADR-0055](../adr/0055-vite-plus-and-pnpm.md) → Consequences). This `tsrs` is the linter only; the typecheck is `effect-tsgo tsrs`, the tsrs that `@effect/tsgo` ships, whatever this pin says. When upgrading `vite-plus` or `tsrs`, check that `pnpm exec vp lint` on a file with a type error and a floating promise still reports both (`typescript(TS2322)`, `no-floating-promises`), also with `OXLINT_TSGOLINT_PATH` set to a missing file (the root `vite.config.ts` must replace an inherited value): a Vite+ that looks for its backend elsewhere fails with `Error running tsgolint`, and a tsrs that speaks a newer tsgolint protocol than Vite+'s oxlint may not be understood. It does not run on Windows, where Vite+ looks for `tsgolint.exe` or `.cmd` instead. Drop the override, the shim and `tsrs` once `effect-tsgo --tsrs-lint vp lint` runs (`@effect/tsgo` 0.68 and later, with oxlint 1.91 or later). | +| `tsrs`, `oxlint-tsgolint` | exact `0.25.0-ts7.1.0-beta` (`tsrs`) in the root `package.json`; `oxlint-tsgolint` overridden to `link:./tools/tsrs-lint-shim` in `pnpm-workspace.yaml` | Vite+'s type-aware lint backend is tsrs's own linter, `tsrs-lint`, through the shim (`tools/tsrs-lint-shim/bin/tsgolint.js`; [ADR-0055](../adr/0055-vite-plus-and-pnpm.md) → Consequences). This `tsrs` is the linter only; the typecheck is `effect-tsgo tsrs`, the tsrs that `@effect/tsgo` ships, whatever this pin says. When upgrading `vite-plus` or `tsrs`, check that `pnpm exec vp lint` on a file with a type error and a floating promise still reports both (`typescript(TS2322)`, `no-floating-promises`), also with `OXLINT_TSGOLINT_PATH` set to a missing file (the root `vite.config.ts` must replace an inherited value): a Vite+ that looks for its backend elsewhere fails with `Error running tsgolint`, and a tsrs that speaks a newer tsgolint protocol than Vite+'s oxlint may not be understood. It does not run on Windows, where oxlint cannot start the `.js` the root `vite.config.ts` names, and Vite+ looks for `tsgolint.exe` or `.cmd` instead. Drop the override, the shim and `tsrs` once `effect-tsgo --tsrs-lint vp lint` runs (`@effect/tsgo` 0.68 and later, with oxlint 1.91 or later). | | `ws` | exact `8.22.1`, an `overrides` entry in `pnpm-workspace.yaml` | One `ws` for every package: `@earendil-works/chord` pins `8.21.0` and the rest resolve 8.22, and each `ws` is a peer variant of `alchemy`, whose two copies then fail `infra`'s typecheck (a union of two `AlchemyContext`s). Drop it once chord allows 8.22, or move it with the newest `ws` chord allows. | | `@cloudflare/computer` | `patches/@cloudflare__computer@0.11.1.patch` | Adds `Workspace.remount()`, which `updateSkills` runs: computer checks a mount's version only at a Workspace's first index ([`../architecture/workspace.md`](../architecture/workspace.md) → _The Skill set_). Drop it once computer can index a mount again; rerun `apps/server/src/workspace/skills.workerd.test.ts` either way. Also update the `bash` routing lists if the Worker Shell changed ([`workers.md`](workers.md) → _The Workspace DO_). | | `@cloudflare/computer`, computerd | read for the file-change signal | The file-change signal ([`../architecture/container.md`](../architecture/container.md) → _File-change signals_) reads computer's change-log tables (`apps/server/src/workspace/change-log.ts`) and span names (`notify.ts`), and needs computerd's `setxattr` on its mount to stay a no-op the kernel reports. When upgrading either, rerun `src/workspace/notify.workerd.test.ts` and `notify.test.ts`, and recheck by hand as that section's _Limits_ says. |