Skip to content

Install via shadcn CLI? Trouble using with a tailwind prefix configured #171

@eluce2

Description

@eluce2

I've implemented this package into a couple of projects now and love the overall experience. But I'm wondering, have you considered exposing the components via a custom shadcn registry, rather than a package?

The primary issue I've run into is how this method doesn't respect my tailwind prefix, but when components are installed via shadcn, there is a replacement that happens. This would also allow much further customizability with the components, but there would still be much value in the headless components such as <RedirectToSignIn /> or the context provider exposed via an installed package

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions