build(dependencies): move 'tailwindcss-animate' to devDependencies

[Jacksonmills]

Converted 'tailwindcss-animate' from a regular dependency to a devDependency across style configurations. This optimizes production builds by excluding development-related assets, enhancing performance and reducing bundle size. No functional dependencies are affected by this change.

Addresses: #5197

[vercel]

@Jacksonmills is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.

[Jacksonmills]

@shadcn I need some guidance on running the /packages/shadcn local cli so that I can test my changes.

I seem to have it running with pnpm --filter=shadcn-ui dev, however I am unsure how to access it in local projects, I tried linking globally but it said there were no binaries in the dir

[smithgeek]

@Jacksonmills What worked for me was running pnpm build to build the cli, then npm link to link globally and then run npx shadcn wherever you want to test it.

[Jacksonmills]

@Jacksonmills What worked for me was running pnpm build to build the cli, then npm link to link globally and then run npx shadcn wherever you want to test it.

Okay thanks I'll try that!

[Jacksonmills]

@smithgeek got it working ty!

[Jacksonmills]

@shadcn am I missing or doing something wrong here?

I seem to always get "tailwindcss-animate" in deps when I test shadcn:dev locally

Thanks

[shadcn]

@Jacksonmills I'll take a look.

Re. running the cli locally. Here's my workflow:

• pnpm www:dev to run the registry (main site).
• pnpm shadcn:dev to run the dev script for the cli.
• In another tab, pnpm shadcn to test the cli.

eg. pnpm shadcn -c ~/Desktop/my-app to test the cli in my-app locally.

• To run the tests, pnpm --filter=shadcn test

[Jacksonmills]

@Jacksonmills I'll take a look.

Re. running the cli locally. Here's my workflow:

* `pnpm www:dev` to run the registry (main site).

* `pnpm shadcn:dev` to run the dev script for the cli.

* In another tab, `pnpm shadcn` to test the cli.

eg. pnpm shadcn -c ~/Desktop/my-app to test the cli in my-app locally.

* To run the tests, `pnpm --filter=shadcn test`

ahh could be I was not running the local www for the updated registry... will test later

that did it! tyty

[Jacksonmills]

@shadcn LMK if I need to change anything else, thanks again for the help!

[Jacksonmills]

Also @smithgeek check out shacn's workflow, seems like the best way to test in full

Maybe worth updating the contribution readme with this for others that might be a bit confused on running it all

I misunderstood but make sure to run this with an actual command from shadcn

e.g. pnpm shadcn <init | add | etc> -c ~/Desktop/my-app