Skip to content

feat(cli): update tailwind export to v4 format#33

Open
seonghobae wants to merge 1 commit intogoogle-labs-code:mainfrom
seonghobae:tailwind-v4-20260423
Open

feat(cli): update tailwind export to v4 format#33
seonghobae wants to merge 1 commit intogoogle-labs-code:mainfrom
seonghobae:tailwind-v4-20260423

Conversation

@seonghobae
Copy link
Copy Markdown

This PR updates the Tailwind export functionality to support the new CSS-first format introduced in Tailwind v4. The handler now generates a CSS string with custom properties instead of a JavaScript theme object.

Fixes #19
Related to #29

This commit updates the Tailwind export functionality to support the new CSS-first format introduced in Tailwind v4.

The  no longer generates a JavaScript theme object. Instead, it produces a CSS string containing custom properties within a  block, which is the standard configuration method for Tailwind v4.

- The handler logic is updated to generate CSS variables.
- The  for the Tailwind emitter is updated to reflect the new string output type.
- Unit tests for the handler are rewritten to assert the correct CSS string generation.
- The main integration test in  is updated to validate the new output format.
- The  field was also added to the root  to unblock the build process in the clean worktree.

Fixes google-labs-code#19
Related to google-labs-code#29
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Apr 23, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@seonghobae
Copy link
Copy Markdown
Author

The implementation for the Tailwind v4 export format is complete and has been fully verified locally with passing builds and tests.

The PR is currently blocked by the check, which requires manual intervention. The code itself is ready for review and merge.

@seonghobae seonghobae marked this pull request as ready for review April 23, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for Tailwindcss version 4.0 & above

1 participant