Jovi 🐨
@jovidecroock.com
1.1K followers 210 following 660 posts
🇧🇪 | he/him | Software Engineer @Shopify | @preactjs.com core maintainer | AI slop fixer | passionate about DX & web perf | opinions are my own
Posts Media Videos Starter Packs
jovidecroock.com
That's fair, I hope AI is able to provide the right answers then in that case
jovidecroock.com
I am saying this looking from my GraphQL/Preact bubble
jovidecroock.com
Anyone know a way to see overall open-source engagement within i.e. a programming language or a GitHub topic? I've been curious as it looks like engagement has dropped (PR/issue creation) while usage has gone up
jovidecroock.com
It would work yes, the easiest way would be to do `render(null, root); render(newComponent, root)` as that would ensure that you aren't updating the previous state
jovidecroock.com
Gotta game the system if your default bundle is a chonker 😅
jovidecroock.com
Signals change the paradigm from, rerender where you create state to rerender where you use state.

It requires a different mindset but ultimately these are free performance gains
jovidecroock.com
Getting OAuth to work in CF is a bit challenging, I documented what I had to do at github.com/bluesky-soci...

Consuming jetstream would probably be done through a durable object which could get costly I think. Maybe their containers solution is better for this
OAuth client in CloudFlare environments · Issue #3292 · bluesky-social/atproto
Describe the bug There's a few issues with implementing the OAuth client in environments like CloudFlare and other WinterCG environments. I have been able to circumvent these myself with a few tric...
github.com
Reposted by Jovi 🐨
danabra.mov
i think migrating away from Vercel hosting is a solid idea. i moved my Next.js blog to Cloudflare (for free) and have been very happy with that

with Next.js 16+ committing to deployment adapters (and Vercel adapter using the same API), we should hold their feet to the fire on the ease of migration
Reposted by Jovi 🐨
bell.bz
There’s never been a better time to switch from Next.js to Astro nitter.net/rauchg/statu...
nitter.net
jovidecroock.com
Not sure what's been happening to the NPM downloads of Preact but we've been going parabolic these past few weeks. I know that downloads don't indicate much but always fun to look at a project you've been working on for 7 years gain popularity

npmtrends.com/@angular/cor...
A chart showing 4 lines, these represent npm libraries and their downloads.

We can see at the bottom angular core have a steady 4m weekly downloads over the last year, then going up we see vue/runtime-dom evolving from 4 million to the current 6million. Going even more up we see the vue library (vue 2) going from 6Million to 8Million and dropping back to 7Million.

At the top we see the Preact library starting the year around 6M and then now at the end going parabolic to 10million weekly downloads
Reposted by Jovi 🐨
jviide.iki.fi
This was a very good read. It's also a good reminder to check our own NPM access token pages and maybe delete old lingering tokens.
The npmjs.com Access Token page. The user dropdown menu is open, with the "Access Tokens" link highlighted.
jovidecroock.com
I mean, I don’t think that solves a lot. I use AI myself, and I genuinely think using AI isn’t a bad thing _but_ if you just submit stuff that you prompt without reading it… yeah nah
jovidecroock.com
I've really had it with AI generated issues and tests, most can't even take the time to read that their test is actually asserting anything. I've just received a PR that asserted nothing - assert(true).tobe(false) - and didn't bother to look at how our tests are structured... OSS being great lately
jovidecroock.com
Gql.tada in the wild, love to hear it 🎉
jovidecroock.com
Growing as a person means using signals... I don’t make the rules @ryansolid.bsky.social does
jovidecroock.com
Also, I have never stopped to say that I love what you're doing for the client-side GraphQL space. Apollo-Client is the most used one out there, thank you for continuously improving it. Pioneering features and superseding the spec, akin to Relay will do a lot for the community.
jovidecroock.com
Generally though, this spec should advance at some stage. It's implemented in GraphQL v17 but I might be doing something wrong in terms of how to push it, I am a bit unsure on all of that.
jovidecroock.com
Do you want to talk this through, I have a transformation that I use for my personal projects. The transformation basically changes all FragmentSpreads to InlineFragments to compile out the fragment-arguments.
jovidecroock.com
Oh gotcha, sounded like something new was coming instead of Fragment Arguments. I have updated the specification to remove all merge conflicts but at this point it's implemented and everything so it will be a time thing to implement it in GraphiQL and get TSC approval.
jovidecroock.com
Signals transform the paradigm from, re-calculate where you create state to re-calculate where you access state.
jovidecroock.com
Can we collectively agree, and maybe point out, that this is not okay... If a code gets compromised then for that short time window it should be able to do none or limited damage.

Anyone with good contacts at npm?
jviide.iki.fi
FWIW, reported this to them via HackerOne yesterday. Got a prompt response back that this is a known low risk issue and that they don't consider this to present a significant security risk.
Reposted by Jovi 🐨
jviide.iki.fi
Seems that NPM too allows TOTP reuse within the time-step window. Seen a similar issue in multiple services over the years.

Per RFC 6238, a TOTP (Time-based One-Time Password) should be single-use. Allowing reuse, even within the short-ish time window, is not ideal (shoulder surfing, phishing etc.)