I guess the middle ground is providing a MediaBunnyError class, right? That way the user can opt into some level of type-safety with an instanceOf check. Not the same, but better than nothing.

I like what neverthrow does, but at the same time, it can get reeeally verbose. Not sure what it would look like for a library like mediabunny.

I tried using swc, but it handles circular imports differently than tsc. That’s why I’m experimenting with rolldown instead.

But Nest.js uses legacy ts decorators, which is supported by oxc, right?
I’m not that familiar with tc39 decorators, but I’d be surprised if that’s what Nest & TypeORM used.

Thanks for the reply, I figured as much, I was hoping there is maybe a “more official” solution, like a vitest-rolldown package.
But I’ll try this, thanks for the reply 🙂

I’m trying to migrate a Nest.js repo from Jest and I know that ESBuild doesn’t handle decorators, that’s why I’m asking.