feat: build a valid config depending on file extension

[juliusmarminge]

This PR makes sure that the content of the built tailwind config always matches what "mode" we're in.

• for .ts configs, we import type as well as export default {} satisfies Config
• for .cjs configs, we do the current behavior (type import via jsdoc and module.exports = config
• for .mjs configs, we do the current behavior but with export default config

for .js configs, we check if we're in a module. if yes, use a ESM config, else use a CJS config

Closes #406

[vercel]

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

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 28, 2024 9:07am

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-template	⬜️ Ignored (Inspect)	Visit Preview		Jan 28, 2024 9:07am

[juliusmarminge]

Yo @shadcn want me to get this up to date and ship?

create-next-app now also generates a .ts file

[juliusmarminge]

hey @shadcn I know you merged #1247 for ts support but this one also supports esm js config for those using that in their projects so i'll keep it open

[shadcn]

@juliusmarminge Yes. I was going to comment that I like your esm config approach here. Let's keep this open. I'll review and merge.