I still can’t believe it 🤩🇭🇺

ICYMI: tsdown can generate single executable files of your Node.js applications!

Read more in the docs
tsdown.dev/options/exe#...

Finally! I had to build a custom solution for this a while back. I’m glad that a build tool can finally handle it for me.
Can it output alpine-ready binaries too? iirc, the officially distributed binaries don’t work on alpine and it looks like this is only fetching official node binaries.

Abstract illustration of a CSS animation in the shape of a series of square that get incresingly rotated. The text reads: CSS animations as state machines.

I feel like this is either very dumb or very clever. Either way, I blogged about it:

Using CSS animations as state machines to remember focus or hover states in CSS only.

patrickbrosset.com/articles/202...

detarkende's Bracket | March Mad CSS Check out detarkende's bracket picks!

Check out my March Mad CSS bracket picks! 🏀

madcss.com/bracket/deta...
#madcss

tbf, this could be done with a good starter template that produces a hono api and a react spa, but everything has to be set up ergonomically.

i’m getting close to achieving this on my pet project, but there are still some things to iron out (e.g. i would love to use Vite for both BE and FE)

Next.js is bringing the backend to the frontend (api routes, SSR, etc). Hono is trying to bring frontend to the backend (hono client components).

I would try to strike a balance where both backend and frontend can be equally important from the ground up. With end-to-end infered type-safety.

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.

@vitest.dev Is there a way to use Vitest with Rolldown today?