[quectophoton]

But... that's like half the reason why I wanted this feature...

Writing a library in TypeScript (with typechecks in CI/CD as devDependencies) and just importing it directly from Node.js...

[rovingeye]

It was the first thing I tried and of course it didn't work.

It might finally be time to switch to Deno or Bun =(

[chamomeal]

I switched to deno for new projects ~1 year ago and it’s only been joy. There’s a shockingly small amount of friction to switch over, and there are so so many benefits

[steve_adams_86]

I have only one issue I've encountered with Deno that mattered (so to speak) and it's probably my fault. I actually created an issue for it (https://github.com/denoland/deno/issues/30433).

My project config is weird (slightly more sophisticated that my repro), so, it's probably on me. Otherwise I absolutely love Deno. It makes TypeScript simple and joyful. It's the simplicity this language/tooling ecosystems badly needs in my opinion. Sometimes I feel like it makes TypeScript feel a bit more like working with Go; you can just throw a main.ts in there and build an excellent CLI from it in minutes.

[steve_adams_86]

Huh, turns out it's a real bug in node resolution: https://github.com/denoland/deno/issues/30444

[throwanem]

I'm glad you've said this. I have a project at nearly a perfect point to try out that cutover. Not that it isn't nice to understand the circa 2018-2022 TS stack, but it sure would be nice not to have to. (Our ancestors had the same discussions about cfront(1). Everything old is new again.)

[preommr]

> It might finally be time to switch to Deno or Bun =(

Bun has been great.

Deno... perhaps the less said, the better.

[agrippanux]

Bun has been awesome for me and my team fwiw

[epolanski]

Build it.

[rovingeye]

I mean, you can just use a loader, as we've all been doing. It's already built, they just didn't implement it properly.