It's hard to miss Ivan Goncharov 🇺🇦's impact on GraphQL! As the emeritus maintainer of GraphQL.js, Ivan has deep knowledge of the specification and has worked tirelessly to improve the project & share his know-how. Thank you Ivan!!

London GraphQL next week! New venue: American Express just across the road (literally!) from Victoria Station. Two great talks and a little recap of some of the things being worked on at the GraphQL working groups! Register so we know how much 🍕to get 😋 guild.host/events/london-…

Had an awesome time reconnecting with the GraphQL community in London! The pace of progress lately has been incredible. Long-awaited features are finally shipping, and some even bigger milestones might be just around the corner... a spec cut this year? 👀

⏰ Midnight deadline! Early bird pricing for #GraphQLConf ends at 23:59 CET tonight. Don't miss your chance to save on our biggest GraphQL celebration this September in Amsterdam. 10 years of innovation, one amazing event! Register now & save USD$300: hubs.la/Q03wL2NS0

🚀 Hot off the Presses: GraphiQL 5 – and it's BEAUTIFUL! Built by Dimitri POSTOLOV with support from our GraphQL Foundation grant program, this update introduces Monaco—the same powerful editor behind VS Code—bringing you: 🔍 IntelliSense, hover tooltips, go-to-definition,

👀

Misuse of fragments is pernicious: 'reusable' fragments tend to grow over time, unnecessarily stressing CPU, memory, storage, and network on both client and server. Janette Cheng is the perfect GraphQLConf speaker to show us How To Use Fragments correctly!

Benjie Gillam, GraphQL TSC member, is back for #GraphQLConf ‘25! We’re excited to hear from him on the keynote stage + during his frontend dev & working group sessions. Join him 8-10 Sept in Amsterdam. Register now & save: hubs.la/Q03DWTG80

I launched the GraphQL Ambassadors program today on stage at #GraphQLConf it’s shaping up to be a brilliant program, you can read more on GraphQL.org

#GraphQLConf may be over, but the momentum continues! If you're still in town, check out this pop-up MCP Server Builder Series hosted by Apollo & featuring speakers Grafbase Platformatic JetBrains & Adewale 🎉 Sign up: luma.com/wh8ts1tm

🌟 Shoutout to Jordan Eldredge, Relay maintainer and nullability champion! From shaping the “true nullability schema” to sharing critical insights, your impact on GraphQL is huge 🙌 #GraphQLStar

👏 From GraphQL Scalars to the conf app & website, from nullability & HTTP to composite schemas, Martin Bonnin is everywhere — contributing, reviewing, and giving solid feedback. Thank you for all you do! 🚀 #GraphQLStar

👏 Urigo is everywhere in GraphQL — a TSC member helping unite vendors, drive composite schemas, and strengthen the whole community. Thank you! 🚀 #GraphQLStar

Great post from Jovi here! Remember: Trusted Document: If you can, you should!

🌟 From GraphQL.js & Relay to DataLoader, GraphiQL, the website & even GraphQL Weekly — Saihajpreet Singh is everywhere in the ecosystem. Huge thanks for your incredible impact! 🙌 #GraphQLStar

Been a while since I posted about RescriptRelay, but it's alive and well! Just shipped v4.0.0, which is the first version to fully embrace the upcoming ReScript v12 release. Also has an interesting feature, the `@ exhaustive` directive. Put that on any union/interface selection

GraphQL error handling sucks. There, I said it. Null checks everywhere, and ambiguity: error, or true null? We've all been there. In this talk, Benjie Gillam shows how to fix GraphQL's biggest mistake in 512 bytes. 👇 youtu.be/odwQUAkmW44

🎉 We just crossed 1,000 subscribers on YouTube! A huge thank you to everyone watching, learning, and building with GraphQL 💜 We drop new videos every Tuesday and Thursday, from deep dives to lightning talks. 📺 Subscribe and join the community: youtube.com/@graphqltv

GraphQL clients aren’t just for fetching data. They’re becoming the backbone of modern platform architecture. Jeff Auriemma (@ApolloGraphQL) explains how and why 👇 youtu.be/yXPQmjMxBco

GraphQL's simple execution algorithm can result in under- and over-fetching, and a choice between N+1 issues or huge promise/futures usage. We need something better. Holistic. Batched. Efficient. Join @benjie.dev's talk -- Grafast: A Declarative Solution to GraphQL's Execution Woes