This might change how we build UI forever

Shadcn's new CLI stuff is unreal. Shadcn/ui, shadui, whatever you want to call it, I'm hyped.

SOURCES

S/O Ph4seon3 for the awesome edit 🙏

[aldayel]

Man, shadcn ui is literally morphing into an entire philosophy at this point

[tobiasjennerjahn]

Watch shadcn become the new bootstrap, with half of the internet using the default look.

[MrFrummel]

12:57 The section about how to understand codebases, or how a thing works deserves its own video.

[cameronball]

dude that diff git config you showed at the end is legendary, my life is changed from today onward. doing PR reviews on my local just got so much easier

[JC-yynf]

I don't see what's so groundbreaking. Maybe I'm not understanding. Seems like just a component library that you download piece-by-piece, with an added benefit that you can prompt AI to modify the look of them.

[hello]

Now I can add untested AI slop into my codebase even faster!

[robbief]

That history lesson / context in the first 5 mins was golden! Helped me understand the why we are where we are now.

[wandenreich]

Shadcn has become the package manager for UIs

[IronMaidzen]

man this is so awsome, i always wanted something like that for PoC projects where you just need UI so people who don't code understand the PoC. I hope they extend this to svelte (they say the might in the FAQ)

[jsebrech]

So ... I just ran shadcn init, added a button, then added a carousel, looked at the code and ... I don't get how this is maintainable.

Let's say you add a button component, and then you come back half a year later and you need a carousel. Shadcn asks you, "do you want to overwrite button?". I mean ... I don't know? If button has changed in those 6 months, I should probably have it be overwritten or the carousel's code might break, but if I do overwrite it then all my other code might break if the button had breaking changes. So if I say "yes", I need to check the changes to button, and if there's any changes at all I need to retest everything across my app (better hope I have good ui test coverage). I could say "no" and test the carousel and if necessary fix the carousel's code if it needs changes to be compatible with button, but the carousel is over 250 lines, and it's not easy code to figure out or to test, and it doesn't come with any automated tests.

So, I guess I should trust that shadcn never has any bugs or breaking changes? Except it will definitely have bugs, because all non-trivial software has bugs, and it doesn't enforce "no breaking changes" in any way, and even that button was non-trivial when I looked at it. And I didn't see any concept of versioning in shadcn. So, as far as I can tell, this is another dependency system, that exists outside of npm, but worse than npm, and a nightmare to maintain? Why would I want that? Because it makes it easier to get started?

Getting started with a new project or component library is NOT that much of a problem for a working developer. Maintaining a codebase once it's out in the field, that's the biggest problem. Any tool that focuses on getting started at the cost of maintenance is a step back, not a step forward. What am I missing here? Why is this being pitched as an improvement?

[tinrab]

I mean, adding stuff to your project is the easy part. If I have a working app, custom setup, weird and specific context deps, components, state, hooks, RQ queries, etc. Then simply copying a template from the web would never work. Could be helpful when bootstrap-ing a new project quickly, but then you'd just end up changing everything.

[koteelok]

Making CLI to avoid reading docs just to read docs afterwards is wild waste of human resources

[Martindooo]

We have an internal tool that is built using Vaadin, as our backend skillset is mainly on the JVM stack. This update allows me much better to build this in nextjs for comparison. Awesome!

[FrontTech-qupe]

why is this cool and scary at the same time

[DrownedLamp]

Shadcnfreude - deriving pleasure from that lack of frustration while creating UIs

[richardantao]

Genuine question: What happens when you customize a Shad component into your own and then Shad releases a new version of that component? How are your custom changes merged with the new version of the component?

[alexandersedeke]

The most frustrating thing about reading documentation to get things running is that it's often outdated, incomplete, or just plain confusing, leading to wasted time and effort. Frequently, it's just minor changes that cause implementation issues. We often end up searching for projects that have already implemented what we're trying to do, just to figure out how to make it work. So, you're absolutely right in saying that seeing an implementation installed and running beforehand would greatly improve the adoption and usage of these tools.

[StefanHayden]

I had to stop 4 mins in just to say this is perhaps the best intro to a tech video I have ever seen. I knew some of it but what a crystal clear intro to a topic before starting on the new thing.

[eyalteiger]

Imagine junior - mid level front end home assignments now

[vicho]

Been using it for 3 days and I already migrated the old react bootstrap stuff with a lot less code. Loving it already