Library is not customizable
The whole point of using Better-auth and Shadcn is to build your own auth. However, my auth components are broken and do not look like my actual application.
I suggest removing the UI components from npm and making them copy/ paste just like shadcn/ui. I was super hyped initially, but it looks like I need to implement the Ui on my own.
Log in to comment and vote
Comments1
daveycodez
May 10, 2025
Better Auth UI uses your shadcn theme. If it’s not working correctly, double check your CSS imports, you might not have the correct path to your node modules from global.css. Also, it does have extensive theming customizability as well via the classNames prop, you can customize the classes of every single element and sub element to your liking, as the package exists today.
Still, I understand the ask for shadcn components you can clone. There is already a task on the Roadmap for this, and I do plan to support that in the future. However to support all of the logic and plugins that Better Auth has, the package route was easier for me to develop.
Even after I do release shadcn registry components, I won’t remove it from npm. I’m sure plenty of people prefer an npm package, and plenty prefer custom installable shadcn components. Both will be supported.