MSManu Shuklainecorpit.hashnode.dev·2d ago · 15 min readCloudflare vitest-plugin v1: the migration guide targets 0.16.0, the last old release was 0.22.0Cloudflare vitest-plugin v1: the migration guide targets 0.16.0, the last old release was 0.22.0 Summary. On 19 August 2026 Cloudflare announced that @cloudflare/vitest-pool-workers is now @cloudflare00
AOAbdullahi Odesanmiinabdspace.hashnode.dev·Aug 11 · 11 min readTesting a Nuxt Monorepo Without Losing Your MindTesting a standard, single-package app is pretty straightforward. But a Nuxt monorepo? That can get messy very fast. When you're dealing with multiple shared packages, utilities, auto-imports, and all00
Mmehdiinmodern-web-dev.hashnode.dev·Aug 5 · 6 min readModernizing Ionic 8 & Angular 22: Moving from Karma, Zone.js & ESLint v8 to Vitest, Zoneless & Flat Config[!NOTE]Target Audience: Ionic & Angular developers looking to modernize starter boilerplate, boost unit test speed by 5x, adopt pure Zoneless change detection, and upgrade to ESLint v9 Flat Config. 00
JLJeremy Longshoreinjeremylongshore.hashnode.dev·Jul 1 · 6 min readgit-with-intent Vitest 4 Migration Pain and IRSB Governance with 104 Moloch TestsEighteen commits across three repos. git-with-intent fought through a Vitest 4 migration that broke CI seven different ways. IRSB shipped v1.4.0 with governance contracts and a 104-test Moloch DAO sui00
DNDavid Nguyenineplus.dev·Jun 5 · 3 min readVoidZero Joins Cloudflare: Vite Stays Open, but Gains Bigger BackingCloudflare has announced that VoidZero is joining Cloudflare. This is a notable update for the JavaScript ecosystem, as VoidZero is the company behind several important developer tools, including Vite00
TPTushar Patilinblog.techtush.in·May 13 · 15 min read📦 Build and Publish a Reusable TypeScript MCP Client SDKThis is Part 8 of the AI Engineering with TypeScript series. Prerequisites: Part 1 · Part 2 · Part 3 · Part 4 · Part 5 · Part 6 · Part 7 Stack: Node.js 20+ · TypeScript 5.x · @modelcontextprotocol/sdk00
Rrecca0120inrecca0120.hashnode.dev·May 2 · 3 min readvitest-fail-on-console: Stop Ignoring console.error in Your TestsOriginally published at recca0120.github.io All tests pass, but the terminal is full of red console.error output. This is common and easy to ignore — the tests passed, after all. But those errors don't appear out of nowhere. Something went wrong; nob...00
Rrecca0120inrecca0120.hashnode.dev·Apr 28 · 6 min readTesting a Filesystem Service with memfs + FakeWatchService: No Disk RequiredOriginally published at recca0120.github.io How do you test a Node.js service that operates on the filesystem? The obvious approach is to create real files under /tmp, run the tests, then clean up. But that comes with problems: slow I/O, inconsistent...00
Rrecca0120inrecca0120.hashnode.dev·Apr 19 · 6 min readShared HTTP Mocks Across a Monorepo: When Fakes Aren''t the Right ToolOriginally published at recca0120.github.io The previous posts covered [DI + Fake + in-memory]({{< ref "/post/di-fake-in-memory-testing" >}}) and [sharing Fakes across a monorepo]({{< ref "/post/monorepo-shared-fake-testing" >}}). That approach has o...00
Rrecca0120inrecca0120.hashnode.dev·Apr 19 · 7 min readShared Fakes Across a Monorepo: One Test Double from Frontend to BackendOriginally published at recca0120.github.io The previous post covered [DI + Fake + in-memory basics]({{< ref "/post/di-fake-in-memory-testing" >}}). This one takes it further, into a scenario most testing tutorials ignore: how frontend, backend, and ...00
