Shadcn just changed forever

If you've been around here for much time at all, you're probably already familiar with how much I love Shad CNN. It's such a good blend of a component library, a style system, and something that actually lives in your codebase. It's always been fully customizable, which is so important when you're building a system that is going to define how everything you build looks and works. But it's still a system that they're providing you. And as a result, a lot of websites just kind of stick with it. I can't tell you how many times I've seen what feel like the exact same tool tip, the exact same drop-own menu, or the exact same toast when something goes

wrong on the site. And it seems like the Shad CN team feels the same way, which is why they just introduced the biggest change they have made to date with Shad CN create. It's always been possible to customize Shad CN, but it's never been put up front quite to this level. They built a whole system for building your own Shad CN. It is so so cool. I'd go as far to say it's based and not just because it's based on top of the new base UI primitives instead of the old Radics UI ones, although you can switch between the two, but because they put a

ton of effort into this. It's really, really cool stuff and I want to demo all the fun things we can do with it, as well as the history of how we got here. If you build applications for the web, I promise this one's going to be worth watching. As always, Versella is not paying us anymore. In fact, I've spent a lot more money on them than they're paying us. Nobody who we're talking about today is paying us except for today's sponsor. I've seen a lot of debate about how useful AI is for writing code. And I get it. For some things, it's just not as helpful as others. But there's one thing that I just refuse to believe AI isn't helpful

for, and that is code review. I cannot tell you how much time AI code review has saved me. And a huge portion of that is thanks to Grapile, today's sponsor. They have the best AI code review I've ever seen. And a big part of how they got there is by fully deeply understanding your codebase. When you set GPI up on a new project, it indexes the whole thing and builds an understanding of it that it uses when it gives feedback. And that deeper understanding really shows in the code reviews that it gives you. I can show you all sorts of examples of it catching regressions and mistakes in my own code bases. Like here, where it realized that

I don't actually have thinking on for the Deepseek V3.1 thinking benchmark in Skatebench. Super helpful. Like I honestly had missed this and it caught it. And that's a mistake that my team might have had to review otherwise. And now it's caught before I bug my team. Seriously, AI code review is one of the most considerate things you can do for your co-workers because you don't have to waste their time if the AI catches those dumb mistakes first. So, sure, it's helpful for me as a small dev working on a small team, but what about big teams like, you know, Nvidia or Post Hog or Storybook or Raycast or even MRA? Turns out it's useful for all of those.

So much so that I bullied them into building this examples page that shows you real PRs in real open source projects that Grappile caught real regressions in. And you can just scroll through this page and see tons of legitimate examples. Let's just click this post hog one. Why not? This PR is trying to fix a bug in batch exports for big query merges. And here is a change that it noticed has an issue. This exception handler catches all exceptions without reraing them, which could silently hide errors after merging. Consider reaing the exception after

merging to ensure the error is properly propagated. Or let's pick this random one from raycast. Is GitHub really down? You know, I seriously bet if GitHub was to use Gravile for their own code reviews, we'd have fewer outages like this. Like, what? Yeah, GitHub just seriously went down when I was filming, but it kind of proves my point. Grappile will prevent regressions in all sorts of services all of the time. And hey, GitHub, if you all want to try Grappile, I'll personally pay for your subscription because the quality of code at GitHub right now is unacceptable. Get faster feedback without wasting your team's time at soyv.link/gile.

I know I said I was really excited, but I don't think you guys understand to what level this is going to make. so many of the things I build a lot less ugly. You can customize everything. You pick your component library, icons, base color, theme, fonts, and build something that doesn't look like everything else. Have you ever seen a component library author call this out up front so directly? Like Shaden was the most customizable option of any component library, arguably in history, because it dumps the code in your codebase so you can change it yourself. Despite that, Shad Cienne's out here directly saying