A new version of npmx has released and it comes with some new additions to package changelog. Now all shorthand for issues, PRs, commits & accounts are supported.

I'll be talking about how nuxt v4.6 went agnostic and shipped `nuxt/server` … and `@nuxt/vite-server` 👀 can't wait to see people using some of these new APIs in the wild 😁 we have some exciting things planned as a team.

3 more days 👀

Vite+ is also a new project. Vite continues to evolve its scope at the same place as always. And the majority of the things Vite+ does is bundle Vite, Vitest, and other tools in a transparent way, so its scope is a bit of a different beast from bun.

I think bun could choose a different approach here, and collaborate with others instead of reimplementing everything in-house. I think collaboration will still wins long term, and this isn't a good strategy.

In this age of unlimited opportunities, slop forks, and reverse engineering, focusing on doing less but better is crucial.

deno added these features in a very different way than bun. the PR shows how deno is forking the API of tools into itself, and is an example, bun also now has its own built-in TypeScript type checker through bun check, and a draft PR to copy the whole of vitest API into bun test

I have my bet casted

Do you have a link about that time for babel? Or are you referring to Sebastian starting Rome? (that happened long after he was out of babel)

2230 commits across 2814 files, 636338 additions, a regular monday

But why not use the projects you're copying directly? Just doing it because you can isn't going to cut it long term. There is a bet here that bun can end up being better than every tool they are forking inside its guts eventually.

if they really are going to play the internal tool only card, i'd be even more convinced this direction isn't sustainable long term

Also, hard to be as good as every other OSS project on the planet

Ya, and they now need to continue to port new changes they are not participating in forever. I don't think this is a good bet.

Except if they manage to get the whole market share, they're committing themselves to track the decisions of these ecosystems. I don't see how this can be sustainable in the long run.

bun is also adding native bun test, tracking the whole vitest API, they are building all of this in-house instead of building bridges with other teams. I think deno attitude was very different, even if it superficially the two commands they just added were supported by them, too.

I don't think they have a chance, in case that makes you feel better

really curious where bun's story ends up in a few years; their scope story has always been at odds with what I believe is healthy for a project, and they keep doubling down on engulfing whole ecosystems