Lenz Weber-Tronic

Your timeline might have quite a lot of butterflies today, and I've seen a bunch of people voicing the opinion that it's just "the libs leaving X". No. It's just impossible to have a technical discourse on a platform that uses an algorithm so tuned to ragebait.

Apollo Client 4.1 is out, go and stream all the things! apollographql.com/blog/stream-al…

@tejask @thekitze PM.

@thekitze I know @phry has ADHD and has good experience with being a dev with it so he can help

have a call with a psych today, *might* get some low dose adhd meds claude pushed me towards this after dumping all my podcast transcripts + voice notes. it says literally the key issue of my life is adhd. my only fear is losing my creativity and flow of ideas... advice from ppl who were/are on adhd meds is appreciated the rest of you pls 🤫

✨“It’s okay if the grammar isn't perfect - the idea is there” ⠀ 🎙️Listen to our new podcast episode on building reliable tools with @phry, Senior Staff SE @apollographql, hosted by @jherr, Blue Collar Coder. 📺YouTube: youtu.be/Yb86d19kiMI 🎧Spotify: shorturl.at/Kz0v2

@jamonholmgren That kind of encapsulation will IMHO also play a big role with AI, as you never need to look far beyond the file that's currently open - a smaller context makes for better code.

@jamonholmgren And stuff like fragment composition & data masking can get you to a point where every component defines individual data needs, still you only have one request per page (you can stream slow parts of the response via defer).

So, I’ve been out of back end for a decade …. what’s the most common/popular modern API system these days? GraphQL seems to be fading hard. Is it the new realtime systems like SSE / websockets? Is it just good old REST? Convex-like, tRPC, what? This is not “what do I personally like best”, I want to know what you’re seeing in the wild. What is most popular/common?

Apollo Client 4.0 is now GA ➡️ apollographql.pulse.ly/q1d30h1qk1 #GraphQL #API #Dev #APIClient #APIOrchestration

@teemu_taskula @jerelmiller Also, please feel free to open issues for questions like this or open in the forum. I'm on this platform only very sporadically at this point.

@teemu_taskula @jerelmiller Is this Apollo Client 3 or Apollo Client 4? In AC4 I'd expect it to be inactive. In AC3 it could be active.

@apollographql is it expected that preloaded queries via `preloadQuery` are considered "active" when later doing `refetchQueries: ['SomeQuery']`? I'm querying `SomeQuery` at a given page but also preloading it for other pages via link hover on that same page.

@pplanchon_ Similar name, different benefit :) GraphQL Codegen's "Fragment Masking" essentially ensures that each component requests what it needs so you never use fields you're not supposed to. Apollo Client's "Data Masking" prevents rerenders if unrelated fields change on top.

day3 of building in public : i have been trying to use apollo client for react the right way for a long time. i was trying to get the data masking right. tbh i dont really see the value : its add so much complexity only to get a bit more safety ? i must be missing something here. but anyway i dont think the feature is made for me : i think its more engineered for big team with a lot of components, all calling differents part of the graphQL tree, where leader wants some order somewhere. i get all the safety i want from the typescript generated type from codegen-cli. i think i will stick with that at the moment. i managed to get all the query in brume frontend to be fully typed, inside of the docker env, using the graphQL schema designed in the go backend.

@Bamboost_HS @jerelmiller Sorry, not really active on this platform anymore. That sounds like a job for the `PreloadQuery` RSC component: #preloading-data-in-rsc-for-usage-in-client-components" target="_blank" rel="nofollow noopener">github.com/apollographql/…

@jerelmiller / @phry I'd like to make a gql request from my html document while my (huge) js bundle loads. What's the best way to pipe that gql request into my Apollo client once my JS app loads? Was thinking the nextJS cache shim but my request could still be in flight

📣 In case you missed it: #GraphQLConf 2025 schedule is live! 🔥 Join us in Amsterdam 8-10 Sept. for deep dives and exclusive #GraphQL talks. Amazing sessions lined up ➡️ hubs.la/Q03s3Gsk0 Early bird pricing ends 13 July: hubs.la/Q03s3Vgy0

@teemu_taskula I'll try to ping a few people internally but I can't make any promises as I don't know the priorities of other teams.

Maybe @phry knows someone that could push this forward?

Anyone at @apollographql that could get this PR merged? Would be awesome to see the Apollo Server - Fastify integration get some love 🫶 github.com/apollo-server-…

Introducing Apollo MCP Server Learn more about how Apollo MCP Server gives you zero-code MCP tool creation, native REST/GraphQL support, and built-in policy enforcement: apollographql.com/blog/getting-s… #GraphQL #MCP #APIOrchestration

@patrick91 @pintswithjack It's the best way of using Apollo Client in Next.js, and even any other data fetching library would need a similar package to support Next.js.

@patrick91 @pintswithjack We're going to drop the label soon, but there should be nothing to keep you from using it right now. The idea of adding "experimental" to the name was more to get people to closely get the README, not to discourage people from using it.

Here's my handle on other social networks 😉 @patrick@farbun.social

Today we are releasing our first alpha of our next major version of Apollo Client 4.0. This is a major milestone as it will be the first major release of Apollo Client in nearly 5 years. Here are some of the major changes in the first alpha that we look forward to 🧵:

But there's also a ton of other changes. `useLazyQuery` has gotten a rewrite, and a lot of the core has been rewritten to be more ergonomic to use outside of React. Lots more to come, but please already try this out now - we need your feedback! github.com/apollographql/…

Today we released Apollo Client 4.0-alpha.0. The biggest two changes: We switched over to rxjs as our observable layer, and we completely revamped the bundling story. That's a big boost for interoperability, general bundle size and tree-shaking. github.com/apollographql/…

This week's GraphQL Star is @phry, a champion for graphql.js and ESM compatibility - thank you for your contributions and for always pushing us to do better!