What's the motivation using obuild over tsdown instead?

[JounQin]

tsdown is alreay there for a long time before obuild's first commit, I'm just confusing which tool should I choose.

And then I saw the following in obuild's README:

🪦 No support for CommonJS output.

It seems unusable personally: un-ts/synckit#235.

---

Don't get me wrong, I'm just trying to understand why obuild is built at the first place, and what's the issues it resolved that tsdown didn't.

[pi0]

Hey! I have written some notes about backstory: unjs/obuild#24

TLDR, two projects can co-exist, really, they allow bundling libs but with very different visions. At the same time, we share a common stack.

Regarding CommonJS support, with Node.js 18 being EOL and all active runtimes supporting ESM and Node.js support of require(esm), it is probably now a practical move for new major versions and libraries.