The 3 worst GraphQL myths: ❌ Everything is POST ❌ All URLs are /graphql ❌ Anyone can query anything One solution destroys all three: Persisted Operations/Trusted documents www.jovidecroock.com/blog/graphql...

I love all the cool experiments that are popping up in my feed. The React model of putting everything into a component feels like it hindered progress. There are lots of cool explorations happening in every framework right now. 2026 will be an exciting year!

GraphQL should be an implementation detail

Also doubles as a visualization of how Preact Signals work!

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

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

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

There’s never been a better time to switch from Next.js to Astro nitter.net/rauchg/statu...

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...

Seeing the impact of my performance efforts in the wild really makes my day github.com/captbaritone...

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.

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

Growing as a person means using signals... I don’t make the rules @ryansolid.bsky.social does

The missing link in JavaScript tooling Some thoughts on the fractured nature of our tools how we could unify them all. I feel like this would remove many barriers framework devs run into. marvinh.dev/blog/unifyin...

Signals transform the paradigm from, re-calculate where you create state to re-calculate where you access state.

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?

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.)

NPM supports switching from Authenticator App (TOTP) based 2FA to more phishing resistant WebAuthn based 2FA. Adding a WebAuthn security key and disabling the Authenticator App is a pretty quick process. For example Apple Touch ID & Windows Hello work! Physical keys work too, but aren't required.

Celebrating the contributions of our amazing community at #GraphQLConf - thank you to our 2025 GraphQL Stars!

Fresh 2 has graduated to beta releases - essentially release candidates before a stable release. Fresh can now act as a Vite plugin, opening the door to HMR, faster boot times, and Cloudflare deployments. deno.com/blog/fresh-a...

I wish I had more time to be involved with JS tooling. There is so much room for improvement there that would push everything forward.

added grouped updates to the preact signals devtools 🎉 thanks to @jovidecroock.com and the team for being open to early contributions 🙏

Being honest, this has been one of the most humbling experiences. I often feel like I need guidance to do my best work and this has been largely steered by our community and a vision I had. This has felt like a real achievement for me, thank you to whoever tries out the beta!

🎉 Preact 11 beta is here! After years of thoughtful development, we're delivering major improvements with minimal breaking changes. Better hydration, forward refs by default, and performance upgrades - all while maintaining the stability you love about Preact X.

I wonder if an LLM will ever write a GraphQL Parser in TypeScript types thinking it won't be an absolute pain.

I love building developer tools but lately as I was reflecting it daunted on me that the impact my work has had is hard or even impossible to measure. Have people had more fun building or made higher quality things due to my work on preact/gql.tada/urql/...?

JS isn’t slow, your code is. the way we disregard performance and exepect to be fast is one of our biggest problems.

devs will be like "why's TypeScript so slow, I don't have that much code" and then at the top of their code it's import React from "react"; import db from "some-huge-database-schema"; import * as Icons from "library-with-10000-icons-reexported"; import gh from "the-entire-fking-github-api-graphql";

GPT-5 would really help you make the best. web-apps

The disappointment when you see @cloudflare.social adding the new OpenAI models but they don't work with the worker bindings types nor with workers-ai-provider.

To anyone pulling HTML element types from react/preact (i.e, `VideoHTMLAttributes`), would it be problematic to switch from exporting an interface to a type (in a major of course), and would you consider that migration cost worth it for better ARIA checking?

Big new exciting stuff tends to land when I go on holidays... All of these new models. My takeaway is that I should take more holidays

🔬 Signals and GraphQL Fragments While GraphQL fragments optimize data fetching, signals can optimize rendering. The future isn't just fetching less, it's re-rendering smarter. www.jovidecroock.com/blog/surgica...

I've been chasing a bug for a while now in Preact where there is a very rare but deterministic case where we'd crash. Thanks to a contributor we got to the bottom of this and I'm forever grateful to people like this that take the time to talk through issues with me

It's remarkable how well Claude can analyze pictures and how little tokens it produces compared to me describing what's on the picture. Took a screenshot, pasted it into claude code and it did the correct thing😅

And... that's another part of the ecosystem to support it github.com/0no-co/gql.t... your GraphQL types will keep working even when your documents get descriptions

Soon GraphQL.Web and Bluejay will support parsing Executable descriptions on Fragment/Variable/Operation Definition nodes. This means that we can now share the use for an operation/variable/fragment over the GraphQL AST. This might look small but...

Man, I just love modeling state in @svelte.dev 🧡 - State vars are just properties on a class - Complex values, like this cursor position, can be $derived from other state. Svelte figures out when to recompute - Go-to definition shows all the usages of that state too

We need a European Sovereign Tech Fund github.blog/open-source/... "Open source software is critical infrastructure, but it’s underfunded. With a new feasibility study, GitHub’s developer policy team is building a coalition of policymakers and industry to close the maintenance funding gap."

Revisit our gql.tada panel from London GraphQL last year: www.youtube.com/watch?v=ZmRw...

Fuse may not have taken off but it had a pretty amazing video showing the power of gql.tada gql-tada.0no.co

Maybe I should do another attempt at something like fuse where we have opinions on - Schema authoring - Ensure types are done well - Persisted operations out of the box Might just be great if it's CloudFlare first class as we could even have infrastructure opinions then.

Sometimes I hear that it was a mistake to build @vendure.io on top of GraphQL. "Too complex", "Can't be cached", "Poor performance", "It was all hype" Yes, every technology has its tradeoffs. I'm keenly aware. There *are* some aspects you need to be mindful of when working with GraphQL.

Look, I've been around a while & remember when we used to bundle with Grunt, then Gulp, then Webpack. So isn't Vite just an incremental take on what has gone before? No - Vite has something that makes it magical. An absolutely sublime plugin API that feel like you can build *anything* with it.

Preact is ready: stackblitz.com/edit/formisc...

In light of my recent episode on @learnwithjason.dev, I decided to write a blog post about State models and signals.

This is honestly a great list! Go check it out to learn about web-dev, the platform, ...

In light of my recent episode on @learnwithjason.dev, I decided to write a blog post about State models and signals.

Some of the benefit of reducing bundle size is also that it usually leads to better practices. So even in a backend service that doesn't care as much about size, it's worth keeping the cleanliness and conciseness up

If anyone is relying on the Preact Root Fragment gist (gist.github.com/developit/f4...), we've just published `preact-root-fragment` as a proper NPM package that users can use instead for a Preact 10 & 11 compatible replacement for render's third arg, `replaceNode`. github.com/preactjs/pre...