Sponsored by
Expense receipts shouldn't require a search party
Adam spent 20 minutes looking for a $36 receipt. His finance team sent three Slack messages. Someone made a sticky note.
Ramp would have matched it automatically the moment he swiped. Auto-coded, in-policy, synced. Nobody had to ask Adam for anything.
This is what finance looks like when it runs itself.
Your team can be Adam. Or they can not be Adam.
What's up, everyone? This week, TanStack explains why AI pushed them into a rebrand, Railway makes DNS failures visible, and Cloudflare gets the final word on what your CDN caches. Let's dive in.
You currently have {{rp_num_referrals}} referrals.
TanStack has a new look, and Tanner Linsley's essay on why is better than the rebrand itself. His argument is that AI made the standard clean developer site cheap to produce, so tidy spacing and consistent colors stopped signaling that anyone cared. The team brought on Andy Beutler as TanStack's first lead designer and turned years of maintainer taste into design tokens, type roles, and a component kit, all public at tanstack.com/ds. He has a point. When a model can generate a passable homepage in a minute, knowing what to refuse becomes an indicator that a person made it.
Railway published its 300th changelog last Friday, and it settles the oldest joke in ops. It is, in fact, DNS, and now you can watch it happen. Every deployment's Network tab includes DNS logs showing each lookup your service makes, with filters like @rcode:NXDOMAIN for misspelled hostnames. Until now those failures surfaced as a generic connection error and left you guessing. The team also added railway api, which searches Railway's live GraphQL schema, describes an operation, and runs it with your CLI credentials, useful for anything the dashboard doesn't cover yet.
shadcn released a Toast component for Base UI projects, with actions, status types, promises, stacking, and swipe dismissal. It installs with pnpm dlx shadcn@latest add toast. A small release, but it's one more sign that the Base UI track is where the new work is happening.
Want to learn more about Payload and how to apply it to your project? Check out my course, Payload Essentials. The course walks you step-by-step through a full Payload and Next.js project so you can go from zero lines of code to a production website ready to deploy.
I believe high-quality education should be as accessible as possible to everyone, no matter where in the world they live. So, purchasing power parity is built in to the price. If you don't see a banner with a discount and believe you should, please let me know!
Cloudflare introduced Cache Response Rules, a rule type that runs after your origin responds but before Cloudflare caches anything. You can strip Set-Cookie, ETag, or Last-Modified, rewrite Cache-Control directives, and set cache tags, all without touching the origin. That fixes the problem where one stray session cookie on a static asset makes it uncacheable and drags every request back to the origin. The rules are available on all plans now.
Cloudflare also open-sourced pvcli, a curl-style CLI for debugging privacy protocols like Oblivious HTTP, the plumbing behind Apple's Private Relay. What used to mean hand-parsing binary bytes against three RFCs is now one command with readable logs. It's Apache-2.0 on GitHub if you want to contribute.
What did I miss? There's so much happening in modern web dev that I know I missed something. Please share your thoughts in the comments or reply to this email. I want to address your suggestions and may include them in future newsletters.
Thanks for reading. See you next time.