Lenz Weber-Tronic

@phry.dev

Maintaining Apollo Client at Apollo GraphQL Redux Toolkit Co-Maintainer Creator of RTK Query Some additional keywords for people to find me: OpenSource, TypeScript, JavaScript, React web: phryneas.de phryneas on most platforms @phry on the bird

*spends HOURS reproducing a browser crash* Claude chuggs along *finally nailed it down, wants to create a reproduction for a bug report* Anthropic: API Error: Claude Code is unable to respond to this request, which appears to violate our Usage Policy. This request triggered cyber-related safeguards.

Use `npm stage publish` they said. It worked great. Use `npm stage approve` they said. "error 409 Conflict" they said. A `graphql-tag` release with `graphql` 17 support might take a little bit longer than expected.

Hey @en-js.bsky.social, I know you're all working on the rust version, and that's great - but are there any plans to release another stable of the babel plugin? From what I see in the playground, it has advanced a lot since 1.0. I would love to use that, but can't justify using the canary.

I'm working on a feature called package maps for Node.js - it's leveraging everything I learned about package resolution these past six years, in a design that's both simple and flexible enough to be backward compatible with existing installs. I'm very excited about this! github.com/nodejs/node/...

loader: implement package maps by arcanis · Pull Request #62239 · nodejs/node

This PR adds a new --experimental-package-map=<path> flag letting Node.js resolve packages using a static JSON file instead of walking node_modules directories. node --experimental-package-ma...

github.com

Incredibly hyped to announce Schema Benchmarks, a project I've been steadily working on in collaboration with @fabianhiller.com! It aims to provide a central and transparent resource for many of the metrics that matter for schemas, including bundle size and runtime performance 😄

Bild

TypeScript doesn't have "Render Types" (unlike Flow, more opinionated toward JSX) This plugin proposes to implement render types constraints as an ESLint plugin Cool idea 👌 This could improve type-safety and prevent many React composition mistakes

horus 🏴‍☠️@horus.dev · 6mo ago

I built an ESLint plugin that enforces which components can be passed as children/props in React. Annotate with a @​renders annotation, get errors when the wrong component is passed. GitHub: github.com/HorusGoul/es...

interface TabsProps {
  /** @renders* {Tab} */
  children: React.ReactNode;
}

<Tabs>
  <Tab />    // ✅ Valid!
  <Button /> // 🚫 Error!
</Tabs>

I've put a lot of work into that apollo-client skill. It contains our latest recommendations on best practices - so if you want to tune out 10 years of outdated blog articles that went into AI training data, add this skill :)

Apollo GraphQL@apollographql.com · 6mo ago

We shipped agent skills for @apollographql.com, GraphQL, and Rust. Get started now with all the docs and best practices to give your agent context to use Apollo Client, Apollo Server, Connectors, and more: https://apollographql.pulse.ly/bxwvizuzmh

I really applaud the work on @npmx.dev, but I just tried the page, and I find it to be extremely overstimulating. It's a *lot* of information on the page at once, and there's no clear distinction between what is "npmx" and "package readme". Hidden buttons and functionality are everywhere.

🚀 Lazy Barrel Optimization in Rolldown Barrel files, files that re-export from other modules, are common in modern JavaScript projects but a nightmare for your build time. Rolldown now has Lazy Barrel Optimization to fix this. Here's how it works 🧵

Rolldown - Lazy Barrel Optimization