Post

After maintaining Tinypool for over 2 years I'm happy to see next version of Vitest dropping it. I've written some reasoning about this in the linked PR. Even though this change is significant for Vitest, I'm more confident about it than making new changes in Tinypool. github.com/vitest-dev/v...

github.comfeat!: rewrite pools without `tinypool` by AriPerkkio · Pull Request #8705 · vitest-dev/vitestDescription Removes Tinypool and adds new custom internal pool for Vitest only. Some previous thoughts I wrote ~2 months ago about this below. Vitest uses tinypool for orchestrating how test file...

21/10/25, 5:47 pm2 reposts27 likes

JauntyWunderKind

@jauntywunderkind.bsky.social

22 Oct 2025

I appreciate the lack of attachment, I appreciate the words. Obviously most of the energy is good here & that seems deserved. Still, makes me more than a bit weirded out to see a shift from dependency to internal thing. Feels like there's a public benefit lost.

AriPerkkio

@ariperkkio.dev

22 Oct 2025

It's mainly because we needed more control of pool architecture on Vitest's side, and didn't want to break Tinypool's public API for all its others users by rewriting everything. Tinypool might be perfect for some users, but for Vitest it was blocker in many ways.