Tom MacWright
@macwright.com
9 months ago jarred wrote about how claude identified and fixed a memory leak in anthropic's sdk (the sdk generator code is from stainless, a separate company) claude's fix was wrong
💬 1
♻️ 0
❤️ 21
jarred wrote about how claude identified and fixed a memory leak in anthropic's sdk (the sdk generator code is from stainless, a separate company) claude's fix was wrong
Whoops, forgot the links:
chriscoyier.net/2023/10/11/r...
remysharp.com/2023/09/26/n... Found it! Looks like originally from @remysharp.com's "404 No More." Looks like you answered Chris's wish:
> Still, I could see this implemented at different levels. Maybe the speed is a solveable problem. Like a browser extension? A WordPress plugin? I remember reading about dead link fallbacks on @chriscoyier.net's blog a couple years ago which I thought was a nifty trick oh man, adam neely's film-length critique of suno is spectacular: www.youtube.com/watch?v=U8dc... fixed it! we shipped a fix that makes the 'screen of death' no longer appear!
You might wonder: What is a panic though? A panic is basically Rust's way of saying "something unexpected happened and I can't safely continue." Or to put it in JS terms: It's like an uncaught TypeError or RangeError crashing your Node process, except it happens at the native/system level.
Rolldown can panic sometimes... but we make sure you never have to!
It's rare, but when it happens, you won't be staring at a cryptic stack trace. @rolldown.rs straight up tells you it is not your code. And a link to report it so we can fix it fast.
Good error messages => good DX Claude Code with Netlify Agent Runners now runs on Opus 4.6 via AI Gateway.
Improved performance over 4.5, same workflow, no action required.
www.netlify.com/changelog/cl... A new community program is landing Monday. Helpers, you’re gonna like this 👀
working on it! :)
great to be a programmer at google, terrible to be a programmer using google. (sorry 🌶️ but this makes ex-google people marginally more annoying than other ex-faang people)
they bundle every sdk with types for every google service (around 320 of them) github.com/googleapis/g... perusing the @val.town npm module cache usage… We're looking for feedback on our new SKILL.md for generated projects! If you're using Tuist's project generation, we'd love to hear your thoughts.
https://community.tuist.... Now GitButler has a CLI!
Stacked and parallel branches, smartlog, simple commit editing, easy undo, json output to every command. And it just works in any Git repo.
Check it out:
blog.gitbutler.com/but-cli 🚨 Reminder: legacy prerendering is being retired by plan tier. If you are still using legacy prerendering, migrate to the Prerender extension(s) before your plan’s cutoff date.
Timeline and next steps:
www.netlify.com/changelog/20... ✨ What's New in ViteLand: January 2026 Recap
◆ Unified redesign across all VoidZero sites
◆ @vite.dev crossed 3 billion npm downloads
◆ @rolldown.rs reached RC status
◆ Lazy Barrel Optimization landed in Rolldown
◆ Oxfmt hit 100% Prettier conformance
◆ ...and more 👀
voidzero.dev/posts/whats-... Questions like this surface often in the community.
If something feels off during setup or upgrade, chances are it’s already been talked through in Discord:
pris.ly/discord In v7, files like enums.js aren’t bundled by default, they’re created when you run prisma generate.
Skip that step, and your imports will fail. This error has come up a few times in Discord 👇
“Upgrading to Prisma v7 and getting `Can't resolve ./enums.js` when importing from a custom client path?”
It usually means the client wasn’t regenerated after the upgrade.