Add back CJS support

Thanks for the great library!

Would it be possible to add back CJS support? There’s still a lot of tooling that doesn’t support ESM yet.

It wouldn’t have to make the tooling for this library more complicated either; for example we use tsup which makes it super easy to bundle for both CJS & ESM: tsup src/index.ts --format esm,cjs.

Happy to open a PR for this.

[codetheweb]

Yeah, I think v4 will probably work fine for now.

Thank you!

[bmakuh]

Hey @codetheweb, sorry for just now responding. Like @chriskrycho my gut instinct is also probably “no,” but on the other hand I’ve been in places before where I’m trying to upgrade something like a webpack plugin that does something funky and relies on some quirk in an older version of Node or something like that. So I hear you when you say that sometimes the ecosystem can lag behind the times in weird ways. Before we go down the road of adding back CJS support, though, I guess one thing I wonder is would it be fine to just stick with True Myth 4 for your use case? True Myth 5 adds some new things but in general it’s not a night and day difference from the last major version—the headline feature mostly was simplifying down to only ESM, haha. My thought is that if TM@4 has suited your needs up until now, would it be possible to hang around on that version until stuff like ts-node or esbuild-register could support monorepos? I only say that getting TM@5 to work with your use case will require a PR either way—a PR to add back CJS support here, or a PR on ts-node or esbuild-register to support monorepos (and the latter PR seems like it would help out other folks in the world too). Thoughts?