A single link and a title isn’t very persuasive to explore a change.
Whilst we know about the built-in test runner, it doesn’t work with other tools such as bun or even vitest, which all come with their own “built-in” variant. So we are then “simplifying” but also restricting.
It also isn’t TypeScript compatible right now which means the TypeScript track (which overlaps greatly in terms of infrastructure) needs more work to… make this work.
What are the upsides of this proposal?
It also isn’t TypeScript compatible right now which means the TypeScript track
It support ts now Support *.ts files for node --test · Issue #55078 · nodejs/node · GitHub now.
What are the upsides of this proposal?
Mainly remove deps for babel and jest, which takes 98M disk spaces.
Babel can only be removed if we commit to only use features that are available in Node LTS, instead of allowing “whatever new shiny thing comes out that reaches stage x”.
We’re not going to rely on a feature that is marked as early development / experimental. (Before anyone comment “yeah but @sebastienlorber.com on Bluesky”, uneven nodes are not stable and not LTS. We will not use them for anything, so this still needs to be available in LTS before we can even consider it).
Mainly remove deps for babel and jest, which takes 98M disk spaces.
We never mind pruning dependencies for something that is “more pure”, but with the tracks switching to PnP and pnpm respectively, the disk space argument isn’t one that will persuade us to do the work to update our entire ecosystem.