I would mention deno as the main competitor

herpdyderp 6 hours ago | parent | next [-]

Personally I much prefer Deno as it's also doing a lot more work to unify the backend and frontend JS APIs.

	▲	dgellow 5 hours ago \| parent [-]
		Yes, same for me. I was skeptical at first but things have really improved over the past 2 years

▲

hungryhobbit 5 hours ago | parent | prev | next [-]

I would too ... but not as the winning competitor.

For their first year two of existence, bun tried to do npm, but better. For the first year or two of their existence, Deno tried to reinvent npm.

The key result is that after that first year or two Deno had to walk back their decisions, to create a Node-ecosystem-compatible tool .. and as a result, they're now significantly behind bun (at least by all metrics I've seen).

	▲	dgellow 5 hours ago \| parent \| next [-]
		I know, early deno was rough and frustrating. But it is now _the_ main competitor to Bun. What makes you say it is behind? Are you talking about features or usage?
	▲	MoonWalk 4 hours ago \| parent \| prev [-]
		Freedom from the NPM mess was why I started my project from the ground up in Deno in the first place.

▲

afavour 5 hours ago | parent | prev [-]

I would mention Node as the main competitor. It isn't moving as vast as the VC-backed ecosystems are but its future is a lot more assured.

	▲	dgellow 5 hours ago \| parent [-]
		Ok, but Node is the status quo. As replacement to the node runtime bun and deno are the two contenders at the moment