Tjta mostly because they can't build stuff. I find people limit themselves into roles. Devs should learn some design why because your can't design shit people will use. Lol No people people should not have to learn everything but understand enough of what other people do. So your able to respect their work. Design is hard
@@jwoods9659 Exactly. I'm tired of people meaning "specialization" as "the sole thing I will do". No, if you want to be productive you need to learn a lot of things from a lots of domains. This doesn't mean being an authority, but at least understanding it good enough you can discuss it with authority.
@@Gornius You gotta remember most developers and designers are nerds. Hince they think a certain way..."mastering" be a "expert". That is the fastest way to be unemployed. You need to have a good working knowledge of skillsets like you said. It takes a lifetime to master this stuff yes. There are people that do, they know everything in it. But that's all they know they are limited to that one thing. And that's fine, but average everyday people.need to be realistic that is not them and most jobs require that you are able to just pick up things and run with it. I say learn how to learn the 20% of working knowledge you need in something and go from that point
I’m a designer. Bridging gaps ⚡️I love this channel for picking up the dev experience. This breakdown of a ui primitive and style config on top is the way 👍
Oh Theo! Currently in my job in building de UI library for our Design System, basically you just described everything im facing with right now, love it!
The idea that designers design and coders code (and each broken down in sub-cubicles) and then throw over the fence is quite antiquated. It was the very thing that "Agile teams" tried to address. Great story in any case. Iris seems like a great designer to team up with.
The designer I work with currently is just like Iris. Always takes his time to help me out when I have issues with the css for a specific design. I would really love to work with someone like him again as I would be leaving the company soon 😔
Honestly, as someone who loves frontend development and actually started their love for development through graphic design, I love stories of devs and designers actually trying to understand each other and it leading to a better solution. I swear, when you stop being so obtuse about your work and you actually let others or even yourself see a problem from a different angle, everything just clicks.
I really like shadcn, but honestly, I've been getting so much mileage out of straight up native html elements with how much the support for them/their apis have improved the past few years, that I probably wouldn't use too many components out of here -- especially given how much custom crap I usually have to end up writing anyway. I'll probably end up sticking to either pure css and/or tailwind for the time being, but I like projects that genuinely get us to re-evaluate how we're doing things. Thanks for the video!
@toparamennoodles9652 I tried using a date picker from shadcn, the imports were around 100KB uncompressed. How is it different than other libraries in this regard?
10:45 My intuition for this is to just apply the background color to a frame that's set on top of the container, which is transparent, and the overflow rule would apply to the background frame instead of the container itself. The color would be applied to the background frame so it doesn't overflow. The button would then sit on top of the container as a sibling element to the background frame, so it could act independently of the background frame's overflow rule.
I learned early in my dev career that designer collaboration is a mandatory consideration. It's so important to be able to interact with an open mind the concerns and technical limitations of design mockups.
WRT overriding a component's styles via className (24:40), you can also reverse the order, for example replace cn(badgeVariants({ variant }), className) with: cn(className, badgeVariants({ variants })
I have been using shadcn for my final year project and have been getting a lot of mileage out of it especially since it is a dashboard UI. And the best part is that it is new enough that they thought I designed the UI from the ground up.
that blog was in my reading list for months now, this vid reminded me of it, good stuff + that css frameworks video of yours is the very first video i watched from you. never subscribed that fast before lol
I just switched from bootstrap to tailwind and shadcn-svelte since last week. I am not a front end dev, but had done a few sites and apps. Initially the first 2 days was a bit frustrating, but after that it was great. Now after a week I find this way is better. Also great on having everything in your project. I had 2 minor changes on copied code, 1 to expose a type on TS. Another is to use a sub component not used by shadcn-svelte but existed underneath.
I am about to try this with Svelte for my own project as well. I just want a good pattern for frontend stuff to make it as painless as I can so that I can focus on backend.
I love shadcn because it does all these behaviours and a11y things properly. I'm not front-end/UI developer, but had to build a quick and dirty UI to interact with an administrative API that I built, and being able to build a decent UI quickly and accurately for the three people who will eventually use it was invaluable.
@11:30 I love designers like this! They are few and far between. I've only ran across a couple like this in my career. Interestingly they were also the both Jr Designers. I loved working with them far more than their Sr. counterparts who I've found to be less flexible and interested in collaborating with eng.
That story about designers remember me about something - similar principle can be applied between testing team and SW engineers in general. In many companies those are in their own 'silos', which always makes me mad as hell, being test engineer who feel to be held back not by SWEs, but others within my 'silo'. When I started to bridge those gaps myself, everything went much better, both side. Less gaps = better.
The recommendation for disabling the behavior to allow consuming projects to override library styles is simple. Don’t remove tailwind merge, just reverse the order and put the className from the props first before overriding with your library styles second. This will read weird if you’re used to reading it the opposite way, but achieves the desired behavior.
Love this blog and video! I hope some piggy backs off this and makes a blog about the shadCn Vue project. Would love to see what they used to replace the react specific libraries. I know that used Vee validate and and a vueZod lib for forms tho.
To be 100% fair, bootstrap originally was to be part of your code base and you would customize it, you would just download zip file and drop the contents into codebase back in bootstrap 1.0/2.0/3.0 days, even 5.x is supposed to still be customizable by using SASS and building up your own set of property variables with the base just being good consistent defaults. But a lot don't bother with customizing to that degree.
"Unlike bootsrap or MUI, with shad ui you have the code in your codebase, it's yours". How is that true if you still have to install radix-ui, tanstack-table, react-date-picker, etc. You are still limited by how much customization the underlying packages allow.
I'm studying how to build a good UI library for a Design system that I created (i'm dev with fundamentals of design) and this video Is really insightful thank you so much
Its nice when you can get a dev and a designer who are willing to work together and compromise. In my (very long) experience, it doesnt happen that often...
I love tailwind-merge and wish it was a first party tailwind solution, but removing it when not needed to be used is sound as that lib is 5kb gzipped and has a runtime cost.
man I tried using Shadcn and I had so much issues with it, specifically the component. In the end I just disabled shadcn and added tailwind styled components. The issue was that with the for some reason the defaultValue is not being handled correctly. I had a dropdown for languages, and for native select, option, it worked without issue. With the shadcn select I could not make it work. It always ignores the default values. Also, i had a list of multiple selectes, which was dynamic I even added a useMemo however the cause so much performance issues that it was unusable in the end. Maybe I suck, but maybe shadcn needs a bit more overhaul to be used on more "serious" usecases.
Select is different in radix vs a normal select. When you use shadcn it just installs a couple dependencies and creates files. When you think of it like another developer in your project created those files it gets a lot more powerful. I have a strong feeling I ran into the same issue last night that you had(the defaultValue issue). My approach was to treat it like a component some developer wrote for me and looked at the file. Figured out it was just radix, looked at the radix docs and solved it pretty quickly after that. It's not an issue with shadcn, it's an issue with radix, and it's really not an issue because radix covers it in their docs. As for the second issue you mentioned, I think you might have been pushing radix outside of its expected use case. You used a hammer as a wrench. Instead of expecting every component to cover every possible use case(just like you'd not expect that of a developer on your team to do) you'd modify the existing component, or add a new component to that folder. You have to shift your thought process a bit. It would take no extra time to have implemented the new select component you made as a new shadcn component. You would have gotten all the benefits shadcn offers on top of it. I don't mean to suggest that you(or anyone) needs to use shadcn. It's just it seems like the issues you had were not caused by shadcn itself and were caused by treating shadcn like it's a normal component library.
@@user-sf8du I get you, but if I need to debug every component I use I kinda just write my own using tailwind, which in the end I did, took me less time then to figure out what was the problem.
That's the thing with shadcn/ui, YOU OWN THE CODE. If there's a bug, it's YOUR problem and you can't simply `npm update` for a patch. You have to maintain it because even if the component works today, a breaking change might introduce a bug when you update one of its dependencies like the Radix component. That's why there's an ever-growing number of github issues. Even some examples on the docs are broken. And for some reason, Shad is even less active on the project. So don't blame yourself man. I think shadcn/ui is great but beware of these caveats.
SOLID principles mentioned in frontend 😂 Honestly very few devs I've come across who work on the UI have come with these skills and its painful to teach every single time.
28:07 This is still simple for forward ref. The hard part is when your component has a generic type and you need a ref prop. React had to make it complicated with forward ref instead of just allowing us to have a regular ref prop that works like any other prop. :D
I will watch the video but before that I just want to said that. I'm not a React developer and I'm bored of the Web but there is one thing I can tell is the approach of chadcn/ui is great and I really glad of the "copy and paste" approach. I think it's better to give to the developer the power of edit the library than just impose all the constraint of the library. Personally I try to create my own "Framework" in Golang but I found myself just editing for each project the core part of my architecture to just follow my hearth. That why tools like "chadcn/ui" are a great inspiration for me cause they show me I can just create a simple CLI who will generate the base component of my "Framework" and if I want to add for example the module React Email, I can just type "my_cli add emails" and tada I copy paste my emails module than I can edit to my will ^^
The forced behaviour of hover opening navigation items in a navbar is what was an immediate deal-breaker for me. Changing a well established and expected default behaviour of a click interaction for the sake of covering a very marginal number of scenarios in the name of 'accessibility' is completely unreasonable.
I believe there are many things to improve, previously when i was working on the project, using new scrollable component in terms of width is was working very nice. But for the height we need to specify the perticular value, other wise it takes full height, and the issue was resizing for responsive ness. Was weird. Other was the form control was giving the bad usestate error normally we can solve that using use effect, but here i was not sure what to use, as the error was comming from the shadcn/ui form. And one was the the popover, when we pass a button to the popover the popup trigger stops working after one time- i think we need to pass some ref to root. And i also noticed sometimes it the variant has the bigger value of style, and you are pass the smaller value while calling the component it doesn't work. If anyone can help me with form please do, i haven't found the solution yet.
i'm using it on a project this week and its really nice. but some components are really different from what i'm used to, specially when handling those informations. hey theo you could do a video that combines shadcn and zod for newbies. sometimes i lose a lot of time on those(im a newbie)
I think shadcn does a good job at making unstyled components but by then not being installed via a package means they can be out of date and could in theory introduce major technical debt if your not careful. Someone at my work had those exact issue where cmdk the lib behind the command component changed and this broke the component. Which wouldn't have happened as easily with a properly maintained headless UI lib
A youtube comment is not a good place to do a deep dive conversation in web development. But I do take issue with your story about the card and popover. There is nothing not doable about the design you were given. Maybe it's because I've been a web developer/engineer since there weren't libraries or consoles. My take is you just manually create the thing you want where you want it in those instances. (Which is essentially what popper does, but if you don't have influence to utilize a library like that I guess i understand why you'd have the designer re work their design) 100% agree on your statement about chain of understanding User to Designer to Engineer.
I watch youtube as I prefer it over reading blog posts. Now I find myself more often watching someone reading a blog post. Not sure what is going on. I look forward to start reading blog posts again that is reacting to youtube videos reacting to blogposts.
12:45 she spent the same amount of time or more than you would have taken to just code the popup to self attatch to the body on mouseover... idk if it is a success story or a story of how lazy you used to be.
I believe Theo misspoke when he said Firefox in regards of DatePicker. In my experience Firefox implements the HTML5 DatePicker to spec. Safari on the other hand flat out refuses to do so.
if you don't want to allow to override certain styles you should put them last in cn call like this cn("can be overridden", className, "can't be overridden")
I wish I could work with a designer in our team. I am designing everything for our admin site and as much I enjoy doing it besides coding it can take up a big chunk of my time.
as designer as dev i'll say one thing, before starting argue with a designer, know that 99,9% of what you're going say is not about limitation but skill issue
@@IlhanNegis you're probably right in plenty of situations but it's also not uncommon for devs to explain those tradeoffs to the stakeholders. It's part of product engineering.
@@Charles-Darwin they are different though, if you pick a badly maintained project then you didn't research. But if it is maintained well and you have a pipeline setup with some level of testing along with mend (or other tool to spot out of date packages), integrating changes as they evolve in the package is more bitesize. You still have potential breaking changes to deal with but at least you are aware of them.
Leave it to JavaScript devs to install 5 npm packages just to enable styling in their project. So tired of this ecosystem and its ceaseless tide of hype and framework-hopping.
Honestly, I don't get the appeal of copy and paste of components. Yes you can modify the code, neat. But I'd rather the components be easy to style and customize, and to have them part of package manager so you get updates and bug fixes as the the components evolve, like they should.
İts kinda ridiculous how you have to make your components in front end instead of relaying on html elements, i dont understand why native html elements are so hard to modify and why they look garbage.
shadcn/ui does indeed present an interesting (and probably an essential) concept; only, they didn't do it right (for everyone). they used tailwind (and the thousands of classes that come with it) when they should have just used plain old css (or at least sass): you say you provide control, you shouldn't opionionate your "control" with a dependency. tailwind is fine if you're prototyping. but for production systems, i prefer clean separation (which tailwind doesn't do with inlining too many classes) between components and styles (using a stylesheet that doesn't mix and match responsibility; that's what css was made for in the first place). I would adopt shadcn/ui when they use css (or scss or at least css-in-js), but as it stands now, it's not for me.
I absolutely hate tailwind, almost as much as I hate reading html. I need meaningful names of components to be able to understand them. To have to break down what some element *is* by *how* it's styled not *what* it's called is just insane and unnecessary cognitive load. I'm not against the utility of it, but they should just roll up some mixins that can be used inside s/css. It's just bootstrap remade a little more flexible.
Thanks for the shoutout Theo. Always a pleasure.
Insightful story about the designers, those guys are heavily under appreciated by us devs
Tjta mostly because they can't build stuff. I find people limit themselves into roles. Devs should learn some design why because your can't design shit people will use. Lol No people people should not have to learn everything but understand enough of what other people do. So your able to respect their work. Design is hard
@9659 Yes it is and any dev worth their salt will understand that and understand the value designers bring
@@jwoods9659 Exactly. I'm tired of people meaning "specialization" as "the sole thing I will do". No, if you want to be productive you need to learn a lot of things from a lots of domains. This doesn't mean being an authority, but at least understanding it good enough you can discuss it with authority.
@@Gornius You gotta remember most developers and designers are nerds. Hince they think a certain way..."mastering" be a "expert". That is the fastest way to be unemployed. You need to have a good working knowledge of skillsets like you said. It takes a lifetime to master this stuff yes. There are people that do, they know everything in it. But that's all they know they are limited to that one thing. And that's fine, but average everyday people.need to be realistic that is not them and most jobs require that you are able to just pick up things and run with it. I say learn how to learn the 20% of working knowledge you need in something and go from that point
It really depends I have worked with designers who knew what they were doing and "designers"
I’m a designer. Bridging gaps ⚡️I love this channel for picking up the dev experience. This breakdown of a ui primitive and style config on top is the way 👍
Oh Theo! Currently in my job in building de UI library for our Design System, basically you just described everything im facing with right now, love it!
The tangent on design was spot on. I'm a UX UI designer and the worst part of the job is working with devs who are not interested in working with you.
I find myself very frustrated most of the time for the same reason… AND IM A DEV.
@@techjandro yeah grenade tossing designers are also a plague
it goes both ways.
@@sayamqazi so true.
wow this video has truly incredible value, learned so much here in a single video thanks theo love you
Ooo i didnt realize this was out. Im so glad work uses tailwind and i am def pushing for shadcn.
Theo audible for blog posts is nice
The idea that designers design and coders code (and each broken down in sub-cubicles) and then throw over the fence is quite antiquated. It was the very thing that "Agile teams" tried to address. Great story in any case. Iris seems like a great designer to team up with.
The designer I work with currently is just like Iris. Always takes his time to help me out when I have issues with the css for a specific design.
I would really love to work with someone like him again as I would be leaving the company soon 😔
Honestly, as someone who loves frontend development and actually started their love for development through graphic design, I love stories of devs and designers actually trying to understand each other and it leading to a better solution. I swear, when you stop being so obtuse about your work and you actually let others or even yourself see a problem from a different angle, everything just clicks.
shadcn deresrves to be the standard way of building modern UI in no time.
It's now offcial v0 design tool
I really like shadcn, but honestly, I've been getting so much mileage out of straight up native html elements with how much the support for them/their apis have improved the past few years, that I probably wouldn't use too many components out of here -- especially given how much custom crap I usually have to end up writing anyway. I'll probably end up sticking to either pure css and/or tailwind for the time being, but I like projects that genuinely get us to re-evaluate how we're doing things. Thanks for the video!
@toparamennoodles9652 I tried using a date picker from shadcn, the imports were around 100KB uncompressed. How is it different than other libraries in this regard?
@ashundeyan8031 go for HTMX then
This library of "reusable" components only works with react or is it compatible with any framework like lit?
10:45 My intuition for this is to just apply the background color to a frame that's set on top of the container, which is transparent, and the overflow rule would apply to the background frame instead of the container itself.
The color would be applied to the background frame so it doesn't overflow. The button would then sit on top of the container as a sibling element to the background frame, so it could act independently of the background frame's overflow rule.
I learned early in my dev career that designer collaboration is a mandatory consideration. It's so important to be able to interact with an open mind the concerns and technical limitations of design mockups.
WRT overriding a component's styles via className (24:40), you can also reverse the order, for example replace
cn(badgeVariants({ variant }), className)
with:
cn(className, badgeVariants({ variants })
The whole video is great, but the dev/design tangent was the highlight for me. Thanks for sharing.
I have been using shadcn for my final year project and have been getting a lot of mileage out of it especially since it is a dashboard UI. And the best part is that it is new enough that they thought I designed the UI from the ground up.
Lmao
that blog was in my reading list for months now, this vid reminded me of it, good stuff + that css frameworks video of yours is the very first video i watched from you. never subscribed that fast before lol
I just switched from bootstrap to tailwind and shadcn-svelte since last week. I am not a front end dev, but had done a few sites and apps. Initially the first 2 days was a bit frustrating, but after that it was great. Now after a week I find this way is better. Also great on having everything in your project. I had 2 minor changes on copied code, 1 to expose a type on TS. Another is to use a sub component not used by shadcn-svelte but existed underneath.
I am about to try this with Svelte for my own project as well. I just want a good pattern for frontend stuff to make it as painless as I can so that I can focus on backend.
@@joelazaro461 not painless but seems more straightforward.
The bit about the design-eng relationship and helping bridge gaps almost made me tear up :')
I love shadcn because it does all these behaviours and a11y things properly. I'm not front-end/UI developer, but had to build a quick and dirty UI to interact with an administrative API that I built, and being able to build a decent UI quickly and accurately for the three people who will eventually use it was invaluable.
@11:30 I love designers like this! They are few and far between. I've only ran across a couple like this in my career. Interestingly they were also the both Jr Designers. I loved working with them far more than their Sr. counterparts who I've found to be less flexible and interested in collaborating with eng.
That story about designers remember me about something - similar principle can be applied between testing team and SW engineers in general. In many companies those are in their own 'silos', which always makes me mad as hell, being test engineer who feel to be held back not by SWEs, but others within my 'silo'. When I started to bridge those gaps myself, everything went much better, both side. Less gaps = better.
The recommendation for disabling the behavior to allow consuming projects to override library styles is simple. Don’t remove tailwind merge, just reverse the order and put the className from the props first before overriding with your library styles second. This will read weird if you’re used to reading it the opposite way, but achieves the desired behavior.
4:39 I don't see anything wrong with Firefox's date picker...
Love this blog and video! I hope some piggy backs off this and makes a blog about the shadCn Vue project. Would love to see what they used to replace the react specific libraries. I know that used Vee validate and and a vueZod lib for forms tho.
To be 100% fair, bootstrap originally was to be part of your code base and you would customize it, you would just download zip file and drop the contents into codebase back in bootstrap 1.0/2.0/3.0 days, even 5.x is supposed to still be customizable by using SASS and building up your own set of property variables with the base just being good consistent defaults. But a lot don't bother with customizing to that degree.
I do my dev work in Firefox and I use native datetime pickers all the time. What’s the issue?
"Unlike bootsrap or MUI, with shad ui you have the code in your codebase, it's yours".
How is that true if you still have to install radix-ui, tanstack-table, react-date-picker, etc. You are still limited by how much customization the underlying packages allow.
Kind of, but worst case scenario you can still replace them.
Bootstrap and MUI aren’t un-styled primitives.
As a final year IT student, shadcn helps me procrastinate even longer 😅
13:00 she is a true MVP 🏆
I LOVE Shadcn. It's just really nice to use.
What was the font size you mentioned in this video? I don't seem to find it again. Thank you!
Datepickers 💀 A couple thousand lines.
forms with multiple datepickers with business rules and validation and 2 way binding ☠
I'm studying how to build a good UI library for a Design system that I created (i'm dev with fundamentals of design) and this video Is really insightful thank you so much
Its nice when you can get a dev and a designer who are willing to work together and compromise. In my (very long) experience, it doesnt happen that often...
I'm using Firefox under Linux, but type="date" shows a very useful and working date picker.
I wonder if there is a list of commonly accepted variance name available ? Some kind of defacto naming. Thanks.
Holy crap, this is perfect.
"We need this in Vue. I have worked on such a library at my previous job. Of course, it was not that advanced, but it sped up development considerably
It exists for vue as well, though unofficially. Google it and you can find it 👍
There is port of shadcn for vue
The CLI part you said is not true, it’s not ‘since just a few months ago’ I installed them over EIGHT months ago using the CLI.
I love tailwind-merge and wish it was a first party tailwind solution, but removing it when not needed to be used is sound as that lib is 5kb gzipped and has a runtime cost.
Why am I getting a feeling of Deja Vu from this video
Because you read the blog post before, just like me 😂
man I tried using Shadcn and I had so much issues with it, specifically the component. In the end I just disabled shadcn and added tailwind styled components.
The issue was that with the for some reason the defaultValue is not being handled correctly. I had a dropdown for languages, and for native select, option, it worked without issue. With the shadcn select I could not make it work. It always ignores the default values.
Also, i had a list of multiple selectes, which was dynamic I even added a useMemo however the cause so much performance issues that it was unusable in the end.
Maybe I suck, but maybe shadcn needs a bit more overhaul to be used on more "serious" usecases.
Select is different in radix vs a normal select.
When you use shadcn it just installs a couple dependencies and creates files. When you think of it like another developer in your project created those files it gets a lot more powerful.
I have a strong feeling I ran into the same issue last night that you had(the defaultValue issue). My approach was to treat it like a component some developer wrote for me and looked at the file. Figured out it was just radix, looked at the radix docs and solved it pretty quickly after that.
It's not an issue with shadcn, it's an issue with radix, and it's really not an issue because radix covers it in their docs.
As for the second issue you mentioned, I think you might have been pushing radix outside of its expected use case. You used a hammer as a wrench.
Instead of expecting every component to cover every possible use case(just like you'd not expect that of a developer on your team to do) you'd modify the existing component, or add a new component to that folder.
You have to shift your thought process a bit.
It would take no extra time to have implemented the new select component you made as a new shadcn component. You would have gotten all the benefits shadcn offers on top of it.
I don't mean to suggest that you(or anyone) needs to use shadcn. It's just it seems like the issues you had were not caused by shadcn itself and were caused by treating shadcn like it's a normal component library.
@@user-sf8du I get you, but if I need to debug every component I use I kinda just write my own using tailwind, which in the end I did, took me less time then to figure out what was the problem.
That's the thing with shadcn/ui, YOU OWN THE CODE. If there's a bug, it's YOUR problem and you can't simply `npm update` for a patch. You have to maintain it because even if the component works today, a breaking change might introduce a bug when you update one of its dependencies like the Radix component.
That's why there's an ever-growing number of github issues. Even some examples on the docs are broken. And for some reason, Shad is even less active on the project. So don't blame yourself man. I think shadcn/ui is great but beware of these caveats.
As a designer, I approve of this message.
SOLID principles mentioned in frontend 😂
Honestly very few devs I've come across who work on the UI have come with these skills and its painful to teach every single time.
I love how much respect you have for every aspect of building products. Except for the poor standards committee on date pickers whom you hate.
28:07 This is still simple for forward ref. The hard part is when your component has a generic type and you need a ref prop. React had to make it complicated with forward ref instead of just allowing us to have a regular ref prop that works like any other prop. :D
As a Designer I wished more people understood our role
11:35 Isn't "position" solve this?
you gotta love theo's miniatures
I will watch the video but before that I just want to said that.
I'm not a React developer and I'm bored of the Web but there is one thing I can tell is the approach of chadcn/ui is great and I really glad of the "copy and paste" approach.
I think it's better to give to the developer the power of edit the library than just impose all the constraint of the library. Personally I try to create my own "Framework" in Golang but I found myself just editing for each project the core part of my architecture to just follow my hearth.
That why tools like "chadcn/ui" are a great inspiration for me cause they show me I can just create a simple CLI who will generate the base component of my "Framework" and if I want to add for example the module React Email, I can just type "my_cli add emails" and tada I copy paste my emails module than I can edit to my will ^^
The forced behaviour of hover opening navigation items in a navbar is what was an immediate deal-breaker for me. Changing a well established and expected default behaviour of a click interaction for the sake of covering a very marginal number of scenarios in the name of 'accessibility' is completely unreasonable.
Couldn’t agree more that it should be easy to build it the accessible way.
Why no one mentions ANT Design tho? This lib is so damn great TBH
Good words about design teams!
I believe there are many things to improve, previously when i was working on the project, using new scrollable component in terms of width is was working very nice. But for the height we need to specify the perticular value, other wise it takes full height, and the issue was resizing for responsive ness. Was weird.
Other was the form control was giving the bad usestate error normally we can solve that using use effect, but here i was not sure what to use, as the error was comming from the shadcn/ui form.
And one was the the popover, when we pass a button to the popover the popup trigger stops working after one time- i think we need to pass some ref to root.
And i also noticed sometimes it the variant has the bigger value of style, and you are pass the smaller value while calling the component it doesn't work.
If anyone can help me with form please do, i haven't found the solution yet.
This is called chad ui and you can't convince me otherwise
This was a great video 👍🏼
i'm using it on a project this week and its really nice. but some components are really different from what i'm used to, specially when handling those informations. hey theo you could do a video that combines shadcn and zod for newbies. sometimes i lose a lot of time on those(im a newbie)
I think shadcn does a good job at making unstyled components but by then not being installed via a package means they can be out of date and could in theory introduce major technical debt if your not careful. Someone at my work had those exact issue where cmdk the lib behind the command component changed and this broke the component. Which wouldn't have happened as easily with a properly maintained headless UI lib
Theo, am i to understanding your point with ref's are like pointers in C/C++, you and point to hell and then go there ;)
Nope. An entirely different concept. A ref in react is an object that is a reference to the underlying DOM object for a given React component.
@@manupadev refs in React are not only to reference DOM Elements, it can be any value.
@@Laura69 Yes Indeed. I should have made the context more clear. I'm specifically talking about element refs.
A youtube comment is not a good place to do a deep dive conversation in web development. But I do take issue with your story about the card and popover. There is nothing not doable about the design you were given. Maybe it's because I've been a web developer/engineer since there weren't libraries or consoles. My take is you just manually create the thing you want where you want it in those instances. (Which is essentially what popper does, but if you don't have influence to utilize a library like that I guess i understand why you'd have the designer re work their design) 100% agree on your statement about chain of understanding User to Designer to Engineer.
how about Park UI ?
I watch youtube as I prefer it over reading blog posts. Now I find myself more often watching someone reading a blog post. Not sure what is going on. I look forward to start reading blog posts again that is reacting to youtube videos reacting to blogposts.
Did he just uploaded a old video?
12:45 she spent the same amount of time or more than you would have taken to just code the popup to self attatch to the body on mouseover... idk if it is a success story or a story of how lazy you used to be.
I believe Theo misspoke when he said Firefox in regards of DatePicker. In my experience Firefox implements the HTML5 DatePicker to spec. Safari on the other hand flat out refuses to do so.
I had to implement it for an internal tool at Twitch in 2018 specifically because Chrome supported it but Firefox didn't if I recall correctly
Really great article
if you don't want to allow to override certain styles you should put them last in cn call like this cn("can be overridden", className, "can't be overridden")
Bro's literally out there reading blog posts jfc
Generational shift represents my early career days 😂
If you know you know
I'm waiting for someone to create gigashad, then i'll use it.
Is everyone fine with that just one select component for example takes 100kb minified?
I wish I could work with a designer in our team. I am designing everything for our admin site and as much I enjoy doing it besides coding it can take up a big chunk of my time.
Must be nice to work with a designer like that, who puts ego aside for the success of their team.
sorry to break at to you but she didn't change how you look at designers, you did realized how you can achive that, while frustrating designer
as designer as dev i'll say one thing, before starting argue with a designer, know that 99,9% of what you're going say is not about limitation but skill issue
@@IlhanNegis It's about balancing the cost (time) of their design decisions with the value of those decisions.
@@alexkaminsky210 that is by definition is not dev's job
@@IlhanNegis you're probably right in plenty of situations but it's also not uncommon for devs to explain those tradeoffs to the stakeholders. It's part of product engineering.
Wouldn't surprise me if shadcn simply becomes standard coding practice moving forward.
Is shadcn codegen?
Still haven't seen any suggestion on how to manage updates/fixes once you've took a cut. You're basically screwed.
npm packages suffer from this for the most part too though
@@Charles-Darwin they are different though, if you pick a badly maintained project then you didn't research. But if it is maintained well and you have a pipeline setup with some level of testing along with mend (or other tool to spot out of date packages), integrating changes as they evolve in the package is more bitesize. You still have potential breaking changes to deal with but at least you are aware of them.
The same way you do with your own custom components. The code is yours.
21:26 This is similar to how Vue does it
so u basicly just read the article
Leave it to JavaScript devs to install 5 npm packages just to enable styling in their project. So tired of this ecosystem and its ceaseless tide of hype and framework-hopping.
Nice
Honestly, I don't get the appeal of copy and paste of components. Yes you can modify the code, neat. But I'd rather the components be easy to style and customize, and to have them part of package manager so you get updates and bug fixes as the the components evolve, like they should.
so basically code gen nice.... 😏
change my mind but browsers and tools should be smart enough nowadays to function without aria stuff..
İts kinda ridiculous how you have to make your components in front end instead of relaying on html elements, i dont understand why native html elements are so hard to modify and why they look garbage.
shadcn/ui does indeed present an interesting (and probably an essential) concept; only, they didn't do it right (for everyone). they used tailwind (and the thousands of classes that come with it) when they should have just used plain old css (or at least sass): you say you provide control, you shouldn't opionionate your "control" with a dependency. tailwind is fine if you're prototyping. but for production systems, i prefer clean separation (which tailwind doesn't do with inlining too many classes) between components and styles (using a stylesheet that doesn't mix and match responsibility; that's what css was made for in the first place). I would adopt shadcn/ui when they use css (or scss or at least css-in-js), but as it stands now, it's not for me.
You could always just fix this in a couple hours for the components you do want, and ignore the rest.
Disagree. This is a bad take.
It's laughable that the person who released this video th-cam.com/video/EtYtYnhxeNc/w-d-xo.html
says that he's an accessibility advocate... :/
What is this app or website he's here? th-cam.com/video/AqmMx_JidGo/w-d-xo.html
Migrating from mui / emotion to this has been an absolute nightmare with my ts app.
I absolutely hate tailwind, almost as much as I hate reading html. I need meaningful names of components to be able to understand them. To have to break down what some element *is* by *how* it's styled not *what* it's called is just insane and unnecessary cognitive load. I'm not against the utility of it, but they should just roll up some mixins that can be used inside s/css. It's just bootstrap remade a little more flexible.
most hyped? by who? youtubers?
Primeiro ?
Honestly I loathe react.