Summary
Six skill files instruct agents to write:
import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
That subpath no longer exists. It was removed in @cloudflare/vitest-pool-workers@0.14.0, when the package moved to a Vitest 4 peer range. Every currently-installable version fails on this import, so an agent following these skills produces a project that cannot start its test runner.
Evidence
./config was dropped at the same release that switched the Vitest peer dependency:
| Version |
./config export |
peerDependencies.vitest |
0.11.0 |
present |
2.0.x - 3.2.x |
0.14.0 |
absent |
^4.1.0 |
0.18.8 |
absent |
^4.1.0 |
0.20.0 |
absent |
^4.1.0 |
0.20.1 (latest) |
absent |
^4.1.0 |
The complete export map in 0.20.1:
{
".": { "types": "./dist/pool/index.d.mts", "import": "./dist/pool/index.mjs" },
"./types": { "types": "./types/cloudflare-test.d.ts" },
"./codemods/vitest-v3-to-v4": { "import": "./dist/codemods/vitest-v3-to-v4.mjs" }
}
The presence of a vitest-v3-to-v4 codemod in the package suggests the migration was intentional and shipped — the skills simply were not updated alongside it.
Affected files
| File |
Lines |
skills/wrangler/SKILL.md |
859, 861 |
skills/durable-objects/references/testing.md |
16, 18 |
skills/cloudflare/references/miniflare/patterns.md |
50, 52 |
skills/cloudflare/references/wrangler/patterns.md |
105, 106 |
skills/cloudflare/references/workflows/patterns.md |
87, 89 |
skills/cloudflare/references/do-storage/testing.md |
9, 11 |
Suggested replacement
cloudflareTest() is exported from the package root and works as a Vite plugin:
import { cloudflareTest } from "@cloudflare/vitest-pool-workers";
import { defineConfig } from "vitest/config";
export default defineConfig({
plugins: [cloudflareTest({ wrangler: { configPath: "./wrangler.jsonc" } })],
});
Verification
Confirmed on 2026-08-03 against @cloudflare/vitest-pool-workers@0.20.1 and vitest@4.1.10, macOS, Bun 1.3.14 as package manager. A Worker with a static-assets binding, configured as above, ran four passing tests against env.ASSETS.fetch() and exports.default.fetch().
Note on impact
This class of error is unusually costly for a skills repository, because the failure surfaces after an agent has scaffolded a project — the config looks plausible, and the error appears only when the test runner starts. Each affected skill also opens with wording to the effect of "prefer retrieval over pre-training, your knowledge may be outdated", which makes a stale snippet inside the skill itself particularly likely to be trusted.
Happy to open a PR fixing all six files if that is useful.
Summary
Six skill files instruct agents to write:
That subpath no longer exists. It was removed in
@cloudflare/vitest-pool-workers@0.14.0, when the package moved to a Vitest 4 peer range. Every currently-installable version fails on this import, so an agent following these skills produces a project that cannot start its test runner.Evidence
./configwas dropped at the same release that switched the Vitest peer dependency:./configexportpeerDependencies.vitest0.11.02.0.x - 3.2.x0.14.0^4.1.00.18.8^4.1.00.20.0^4.1.00.20.1(latest)^4.1.0The complete export map in
0.20.1:{ ".": { "types": "./dist/pool/index.d.mts", "import": "./dist/pool/index.mjs" }, "./types": { "types": "./types/cloudflare-test.d.ts" }, "./codemods/vitest-v3-to-v4": { "import": "./dist/codemods/vitest-v3-to-v4.mjs" } }The presence of a
vitest-v3-to-v4codemod in the package suggests the migration was intentional and shipped — the skills simply were not updated alongside it.Affected files
skills/wrangler/SKILL.mdskills/durable-objects/references/testing.mdskills/cloudflare/references/miniflare/patterns.mdskills/cloudflare/references/wrangler/patterns.mdskills/cloudflare/references/workflows/patterns.mdskills/cloudflare/references/do-storage/testing.mdSuggested replacement
cloudflareTest()is exported from the package root and works as a Vite plugin:Verification
Confirmed on 2026-08-03 against
@cloudflare/vitest-pool-workers@0.20.1andvitest@4.1.10, macOS, Bun 1.3.14 as package manager. A Worker with a static-assets binding, configured as above, ran four passing tests againstenv.ASSETS.fetch()andexports.default.fetch().Note on impact
This class of error is unusually costly for a skills repository, because the failure surfaces after an agent has scaffolded a project — the config looks plausible, and the error appears only when the test runner starts. Each affected skill also opens with wording to the effect of "prefer retrieval over pre-training, your knowledge may be outdated", which makes a stale snippet inside the skill itself particularly likely to be trusted.
Happy to open a PR fixing all six files if that is useful.