cenobite, a hardened test runner with single-process isolation built on node:test:
github.com/boneskull/ce...
github.com/boneskull/ce...
GitHub - boneskull/cenobite: A hardened test runner using Secure EcmaScript (SES)
A hardened test runner using Secure EcmaScript (SES) - boneskull/cenobite
github.com
October 10, 2025 at 9:46 PM
cenobite, a hardened test runner with single-process isolation built on node:test:
github.com/boneskull/ce...
github.com/boneskull/ce...
@cjihrig.bsky.social I gave you props in the readme. great work on node:test
September 8, 2025 at 7:58 PM
@cjihrig.bsky.social I gave you props in the readme. great work on node:test
Let's pour one out for uvu: a very nice test runner for Node.
It was extremely useful for us when we needed something simple and fast, but now it's time for us to move to node:test.
Thanks uvu! And many thanks to it's creator @lukeed.bsky.social!
github.com/lit/lit/pull...
It was extremely useful for us when we needed something simple and fast, but now it's time for us to move to node:test.
Thanks uvu! And many thanks to it's creator @lukeed.bsky.social!
github.com/lit/lit/pull...
[labs/analyzer] Convert uvu tests to node:test by justinfagnani · Pull Request #5071 · lit/lit
This is a large change by line count, but it was all fairly mechanical. I verified that the same number of tests run and pass after the conversion. Before was 17 node:test, 437 uvu. After 454 node:...
github.com
August 27, 2025 at 10:12 PM
Let's pour one out for uvu: a very nice test runner for Node.
It was extremely useful for us when we needed something simple and fast, but now it's time for us to move to node:test.
Thanks uvu! And many thanks to it's creator @lukeed.bsky.social!
github.com/lit/lit/pull...
It was extremely useful for us when we needed something simple and fast, but now it's time for us to move to node:test.
Thanks uvu! And many thanks to it's creator @lukeed.bsky.social!
github.com/lit/lit/pull...
I enabled the recommended type-checked typescript-eslint rules in a project using the Node.js test runner (`node:test` built-in package) and learned that the `describe` and `it` functions return `Promise` 🫤 Found this great issue from @joshuakgoldberg.com 💙
node:test APIs returning Promises clashes with no-floating-promises lint rule · Issue #51292 · nodejs/node
Version 21.5.0 Platform n/a Subsystem node:test What steps will reproduce the bug? Write code that calls a describe, it, or test function imported from node:test Lint that code with @typescript-esl...
github.com
August 2, 2025 at 7:34 PM
I enabled the recommended type-checked typescript-eslint rules in a project using the Node.js test runner (`node:test` built-in package) and learned that the `describe` and `it` functions return `Promise` 🫤 Found this great issue from @joshuakgoldberg.com 💙
Testing+mocking with node:test
Worker with node (web and « old » one)
Giagnostic
Worker with node (web and « old » one)
Giagnostic
July 3, 2025 at 5:46 PM
Testing+mocking with node:test
Worker with node (web and « old » one)
Giagnostic
Worker with node (web and « old » one)
Giagnostic
Node.js v24.3.0リリース。
`--experimental-transform-types`の警告を削除、`node:test`でプロパティのモックをサポート、`url.fileURLToPathBuffer()`を追加など "Node.js — Node v24.3.0 (Current)" https://nodejs.org/en/blog/release/v24.3.0 #nodejs #ReleaseNote
`--experimental-transform-types`の警告を削除、`node:test`でプロパティのモックをサポート、`url.fileURLToPathBuffer()`を追加など "Node.js — Node v24.3.0 (Current)" https://nodejs.org/en/blog/release/v24.3.0 #nodejs #ReleaseNote
June 26, 2025 at 12:31 AM
Node.js v24.3.0リリース。
`--experimental-transform-types`の警告を削除、`node:test`でプロパティのモックをサポート、`url.fileURLToPathBuffer()`を追加など "Node.js — Node v24.3.0 (Current)" https://nodejs.org/en/blog/release/v24.3.0 #nodejs #ReleaseNote
`--experimental-transform-types`の警告を削除、`node:test`でプロパティのモックをサポート、`url.fileURLToPathBuffer()`を追加など "Node.js — Node v24.3.0 (Current)" https://nodejs.org/en/blog/release/v24.3.0 #nodejs #ReleaseNote
Trying to build a cross-runtime test suite that works on Node.js, Bun, and Deno, but hitting a roadblock with Bun's incomplete `node:test` implementation. Missing subtests/test steps support is making this harder than it should be.
Support the `node:test` built-in API · Issue #5090 · oven-sh/bun
What is the problem this feature would solve? As part of evaluating/migrating to bun from node, it is cumbersome to use both node:test and bun:test at the same time. What is the feature you are pro...
github.com
June 23, 2025 at 11:18 AM
Trying to build a cross-runtime test suite that works on Node.js, Bun, and Deno, but hitting a roadblock with Bun's incomplete `node:test` implementation. Missing subtests/test steps support is making this harder than it should be.
A good reason to use node:test is that you can focus on upgrading your runtime, instead of upgrading dependencies.
June 23, 2025 at 6:38 AM
A good reason to use node:test is that you can focus on upgrading your runtime, instead of upgrading dependencies.
I'm amazed by how fast Piscina's tests get after moving to node:test
Thanks @pmarchini for the contribution!
Thanks @pmarchini for the contribution!
June 19, 2025 at 9:14 AM
I'm amazed by how fast Piscina's tests get after moving to node:test
Thanks @pmarchini for the contribution!
Thanks @pmarchini for the contribution!
I'm preparing a lightning talk: 10min of live-coding a little app to showcase newer features in @nodejs.org, and how they replace the need for common packages.
- dotenv with --env-file
- nodemon with --watch
- ts-node with native @typescriptlang.org support
- etc..
Now looking for app ideas 💡👀
- dotenv with --env-file
- nodemon with --watch
- ts-node with native @typescriptlang.org support
- etc..
Now looking for app ideas 💡👀
June 11, 2025 at 8:52 PM
I'm preparing a lightning talk: 10min of live-coding a little app to showcase newer features in @nodejs.org, and how they replace the need for common packages.
- dotenv with --env-file
- nodemon with --watch
- ts-node with native @typescriptlang.org support
- etc..
Now looking for app ideas 💡👀
- dotenv with --env-file
- nodemon with --watch
- ts-node with native @typescriptlang.org support
- etc..
Now looking for app ideas 💡👀
If something supports something, it doesn’t mean you can just replace one part of it with another. All vitest features are integrated with each other. You can’t just say since one part can run tests, let’s ask it to run them with node:test or something. Vitest is vitest
June 3, 2025 at 5:45 AM
If something supports something, it doesn’t mean you can just replace one part of it with another. All vitest features are integrated with each other. You can’t just say since one part can run tests, let’s ask it to run them with node:test or something. Vitest is vitest
Bun에서 `node:test` 모듈을 쓸 수 있긴 한데, 모든 기능을 다 제공하는 건 아니라서 이것에 의존하기가 어렵다. (적어도 내가 돌리려는 테스트는.)
May 25, 2025 at 4:32 AM
Bun에서 `node:test` 모듈을 쓸 수 있긴 한데, 모든 기능을 다 제공하는 건 아니라서 이것에 의존하기가 어렵다. (적어도 내가 돌리려는 테스트는.)
I would be mostly interested in using node:test for my npm modules, but since I support all current LTS releases it will be a very long time until I can use these additions
May 12, 2025 at 8:09 AM
I would be mostly interested in using node:test for my npm modules, but since I support all current LTS releases it will be a very long time until I can use these additions
Big high five to @puppo92.bsky.social 🙏! He singlehandedly migrated Pino's test suite over to `node:test`. These PRs, and the cooperation on them, are a prime example of what we look for in community contributions.
May 9, 2025 at 12:21 PM
Big high five to @puppo92.bsky.social 🙏! He singlehandedly migrated Pino's test suite over to `node:test`. These PRs, and the cooperation on them, are a prime example of what we look for in community contributions.
Happy Node.js EOL day everyone!! 🎉🎉🎉
This is a big one y'all.
Let's all start enjoying
- require(esm) 😱
- Built-in test runner with node:test 🤩
- import.meta.resolve() 🔭
This is a big one y'all.
Let's all start enjoying
- require(esm) 😱
- Built-in test runner with node:test 🤩
- import.meta.resolve() 🔭
a man wearing a party hat eating a cupcake
Alt: a man wearing a party hat eating a cupcake
media.tenor.com
May 1, 2025 at 2:57 PM
Happy Node.js EOL day everyone!! 🎉🎉🎉
This is a big one y'all.
Let's all start enjoying
- require(esm) 😱
- Built-in test runner with node:test 🤩
- import.meta.resolve() 🔭
This is a big one y'all.
Let's all start enjoying
- require(esm) 😱
- Built-in test runner with node:test 🤩
- import.meta.resolve() 🔭
TypeScript's types for `assert` need to level up their game. when they do, it'll make node:test ridiculously better than the competition.
April 18, 2025 at 6:36 PM
TypeScript's types for `assert` need to level up their game. when they do, it'll make node:test ridiculously better than the competition.
@nodejs.org’s website now entirely tests on the `node:test` module! This took a lot of work from a lot of people, and we are all so happy to see it come to fruition!
Cheers, everyone!
github.com/nodejs/nodej...
Cheers, everyone!
github.com/nodejs/nodej...
chore(test): migrate from Jest to `node:test` by avivkeller · Pull Request #7623 · nodejs/nodejs.org
This PR replaces Jest with node:test as the test runner. While it's currently marked as a draft, it's functionally complete (aside from some GitHub Actions that still need testing), so feel...
github.com
April 18, 2025 at 2:12 AM
@nodejs.org’s website now entirely tests on the `node:test` module! This took a lot of work from a lot of people, and we are all so happy to see it come to fruition!
Cheers, everyone!
github.com/nodejs/nodej...
Cheers, everyone!
github.com/nodejs/nodej...
Deno v2.2.10 is out 🎉
⭐ Faster deno install with npm
⭐ improved node:test
⭐ stream and querystring fixes
⭐ virtio VSOCK on Linux
and more!
github.com/denoland/den...
⭐ Faster deno install with npm
⭐ improved node:test
⭐ stream and querystring fixes
⭐ virtio VSOCK on Linux
and more!
github.com/denoland/den...
Release v2.2.10 · denoland/deno
Upgrade
deno upgrade
Or install for the first time
curl -fsSL https://deno.land/install.sh | sh
New features
using keyword support: Adds support for using, DisposableStack, and AsyncDisposableSt...
github.com
April 16, 2025 at 6:30 PM
Deno v2.2.10 is out 🎉
⭐ Faster deno install with npm
⭐ improved node:test
⭐ stream and querystring fixes
⭐ virtio VSOCK on Linux
and more!
github.com/denoland/den...
⭐ Faster deno install with npm
⭐ improved node:test
⭐ stream and querystring fixes
⭐ virtio VSOCK on Linux
and more!
github.com/denoland/den...
node:test is the best test runner because it runs on both node and bun
April 4, 2025 at 12:07 AM
node:test is the best test runner because it runs on both node and bun
Today I finally got that typescript test working, that tests a generator function, which uses an API and streams the results over SSE.
Copilot was not helpful, as I was trying really hard to use undici and node:test. Always trying to force me to use jest and sinon. 😮💨
Copilot was not helpful, as I was trying really hard to use undici and node:test. Always trying to force me to use jest and sinon. 😮💨
April 1, 2025 at 5:44 PM
Today I finally got that typescript test working, that tests a generator function, which uses an API and streams the results over SSE.
Copilot was not helpful, as I was trying really hard to use undici and node:test. Always trying to force me to use jest and sinon. 😮💨
Copilot was not helpful, as I was trying really hard to use undici and node:test. Always trying to force me to use jest and sinon. 😮💨
I have eg. had regressions in node:test made updates problematic – making what would otherwise be a dev dependency cause issues with upgrading to a newer node.js version
If I could have pinned just the node:test version that would have fixed it.
(Instead I became a maintainer of Mocha)
If I could have pinned just the node:test version that would have fixed it.
(Instead I became a maintainer of Mocha)
March 31, 2025 at 4:52 PM
I have eg. had regressions in node:test made updates problematic – making what would otherwise be a dev dependency cause issues with upgrading to a newer node.js version
If I could have pinned just the node:test version that would have fixed it.
(Instead I became a maintainer of Mocha)
If I could have pinned just the node:test version that would have fixed it.
(Instead I became a maintainer of Mocha)
One could say the same thing for node:test over npm installing mocha, parseArgs over minimist/yargs, undici/fetch over axios/node-fetch, node:sqlite over node-sqlite3, etc.
Maybe corepack is on the wrong side of the balance, but it does feel comparable.
Maybe corepack is on the wrong side of the balance, but it does feel comparable.
March 24, 2025 at 11:09 AM
One could say the same thing for node:test over npm installing mocha, parseArgs over minimist/yargs, undici/fetch over axios/node-fetch, node:sqlite over node-sqlite3, etc.
Maybe corepack is on the wrong side of the balance, but it does feel comparable.
Maybe corepack is on the wrong side of the balance, but it does feel comparable.
Finalizing rewrite of AST-aware v8-to-istanbul. This will provide accuracy of Istanbul coverage for V8 coverage reports. I've intentionally kept this tool unopinionated so that it's not strictly tied to just @vitest.dev - it should be usable with Jest, C8, Playwright and node:test too.
March 21, 2025 at 9:42 AM
Finalizing rewrite of AST-aware v8-to-istanbul. This will provide accuracy of Istanbul coverage for V8 coverage reports. I've intentionally kept this tool unopinionated so that it's not strictly tied to just @vitest.dev - it should be usable with Jest, C8, Playwright and node:test too.
node:test isn't _that_ yet, the DX isn't comparable to other mature libraries
March 17, 2025 at 10:38 PM
node:test isn't _that_ yet, the DX isn't comparable to other mature libraries