Janis Jansen 🌳

I'll look into that! Sounds like the consequence of using a framework that's still in alpha :)

Waku, the minimal React framework A lightweight React server components framework with a fun developer experience.

There is A LOT of stuff that doesn't work yet of course. I have to figure out to what extend this should be a client for each integration. Right now, probably we should just always redirect.

I built it with waku.gg and damn was it a good experience. It's fast and cloudflare support is built-in.

The cool thing is that there are some pre-defined "blocks" that the integrations use. So adding new integrations is as easy as translating their lexicons to the in-app format.

Ideally, we would even use something like @inlay.at and let users define their UI.

Created an app today that shows all your at://proto activity in your own personal garden: profile.garden

It's fully vibe-coded right now apart for some UI stuff. My goal is that you can login and can customize your garden. Integrations include bsky, tangled, stream.place, popfeed, @npmx.dev etc.

npmx.social +1 now.

Honestly magical how smoothly this went with MOOver by @baileytownsend.dev.

My PDS is now 13 train stops away from me.

I worked in an sph company for years and this was a very good write-up with some nice links.

I use @rolldown/browser. Vite probably uses just `rolldown` though? So without knowing the code, it would surprise me if they would use the same rolldown instance under the hood?

So if I just to
const instance = await rolldown(..)
and don't call
rolldown.close()

vite works perfectly fine. That made me think: Either closing rolldown here crashes my plugin, or the two rolldown instances use the same binding or something like that?

I have a vite plugin that basically creates a rolldown (@rolldown/browser) instance like

await using instance = await rolldown(...)

if this is disposed (at the end of my function) the vite build just stops entirely. No errors, no logs, nothing. However, if I don't dispose this, everything works!

Question for my @rolldown.rs folks before I open an issue:

If I "manually" create a rolldown instance in a rolldown-vite app, e.g in a vite plugin, is there any connection between my manually created rolldown instance and the one vite uses?

Asking because of an interesting bug/issue I had: 🧵

I didn't know there was a fork by eslint! Nesting support is a must.

I love the postcss API for the reason that it allows you to do anything basically. For my case I prefer flexibility over spec compliance.

Oh wait. Is this not an LLM input?

What's the best alternative to PostCSS for building CSS ASTs? Csstree?

TIL postcss is cjs-only. But I think there is motivation to change that, which is awesome. As always just a matter of compatibility.

"this is urgent from our end. It blocks us in making a $100k Deal with a customer."

Just had a "oh, LLMs really still suck" moment and that made me happy.

2026 will be grrreat

Sounds like something @tangled.org already thought about?

Idea: ATProto-based vouching/trusting to allowlist (or block) GitHub PRs. If you're not verified (like on bluesky) you can't PR. Could get rid of AI slop.

Yes, it will be horrible at the start and at the end, but there will be a sweet spot where it works super nicely!

Is this data available somewhere? So much I want to explore.

This is super cool. I'm neighbors with @jquery.bsky.social and @wasm.io. can't get more precise than that.

Also in there: @hiogawa.bsky.social, @joshuakgoldberg.com and @daishikato.com along with the ones I mentioned before.

Thank you all for your work, it truly has a huge impact!

ElevenLabs Engineers OSS Fund for open-source projects We are launching the ElevenLabs Engineers OSS Fund to provide recurring support for the open-source projects that power our audio and AI systems.

Grateful for being part of the first round of the OSS Engineering Fund by @elevenlabs.io 💖

Thank you for sponsoring me 🙏

Sponsor @patak-dev on GitHub Sponsors Hey! I'm one of the Project Stewards of [npmx](https://npmx.dev). We're building a modern browser for the npm registry, by fostering an ever growing community of developers and trying to set an exa...

I just sponsored @patak.dev for his work on npmx (and all the other stuff). I love this project and think it deserves backing. Hoping some day I find time to contribute.

Sponsor your open source maintainers!!

github.com/sponsors/pat...

Wanted to be the first for is-even... but I was too late.

first to like postcss by @evilmartians.com on @npmx.dev

Would be super cool to have some kind of node-modules.dev like dependency diagrams btw. Might be overkill, idk.

Everything about that setup is perfect

10/10 as always!

That makes me think there already is (or soon might be?) an automated way to do this?

a-la `npx use-better-packages` for package.json substitutions.

Wow is there a list of packages and their alternatives?