feat(esm): Support running Tailwind setup in ESM projects

[Tobbe]

The code comment explains this pretty well

// `tailwindcss init` will generate ESM syntax when it detects
// `"type": "module"` in package.json, even though the config
// file is .cjs. So we change it back to CJS syntax after it's
// been generated.

This is part of the ESM prep work started in #349

[netlify]

✅ Deploy Preview for cedarjs canceled.

Name	Link
🔨 Latest commit	dfa5ee1
🔍 Latest deploy log	https://app.netlify.com/projects/cedarjs/deploys/6897483cf71d140008998a28

[greptile-apps]

Greptile Summary

This PR addresses a specific issue with TailwindCSS configuration generation in ESM projects within the Cedar framework. The change modifies the tailwindcssHandler.js file to fix a behavioral quirk where TailwindCSS's init command automatically generates ESM syntax (export default {) when it detects "type": "module" in a project's package.json, even when targeting a .cjs configuration file.

The solution implements a simple string replacement that converts the generated ESM export syntax back to CommonJS (module.exports = {) after the Tailwind config file is created. This ensures that Cedar's .cjs configuration files maintain proper CommonJS syntax regardless of whether the project is configured for ESM or CJS modules.

This change fits into Cedar's broader ESM preparation work (referenced as part of #349) and maintains the framework's consistent approach of using .cjs files for configuration that need to work across both module systems. The fix is surgical and targeted, only affecting the specific case where TailwindCSS generates incompatible syntax, while preserving all other functionality of the Tailwind setup process.

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it addresses a specific compatibility issue with a simple, well-documented fix
• Score reflects the targeted nature of the change, clear problem identification, and proper solution that maintains backward compatibility
• No files require special attention as the change is isolated to a single handler with clear purpose and scope

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}