I had been considering that perhaps Bun's (way-too-late IMHO) ESM/CJS flexibility as not necessarily desirable. The package ecosystem has really firmed up ESM support from dev pressure on projects over the past year or so, but consider what would happen if projects were just like "Works in Bun, won't fix shrug". That's a fracture right there over library compatibility.

But looking at this PR has me wondering about generally project compatibility. Imagine a project going all-in on Bun and now it won't even work with Node; even if just for contributions due to using their test runner or some such.

Some juicy drama ahead as a VC venture tries to slice up and control a pieced of the Node ecosystem pie. And I thought the drama with all the framework baiting hosting companies(Vercel, etc) was good with them trying to control the stack narrative around server components..

I expected this to be somehow related to https://groups.google.com/g/comp.sys.amiga.misc/c/7AdXvE7KQz...