fix: rename tailwind export formats for clarity and backwards compat#64
Merged
Conversation
Rename export format flags to avoid 'Tailwind CSS' product name confusion and restore backwards compatibility: - css-tailwind: Tailwind v4 CSS @theme block (new) - json-tailwind: Tailwind v3 theme.extend JSON - tailwind: backwards-compatible alias for json-tailwind The output-first naming (css-*, json-*) tells the user what they'll get before which tool it targets. Bare 'tailwind' preserves existing behavior (JSON output), preventing a breaking change from PR #45. Updates README.md export section and interop docs to reflect new naming.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renames the export format flags introduced in #45 to avoid the "Tailwind CSS" product name confusion and restore backwards compatibility.
Before (PR #45)
--format tailwind@themeblock--format tailwind-v3theme.extendAfter (this PR)
--format css-tailwind@themeblock--format json-tailwindtheme.extend--format tailwindjson-tailwind)Why output-first naming?
tailwind-cssreads like the framework's own name ("Tailwind CSS") — confusingcss-tailwindreads as "CSS output for Tailwind" — the output type leadscss-tailwindimmediately knows it gets CSS;json-tailwindmeans JSON--format tailwindstays backwards-compatible (JSON output, same as before feat: add Tailwind CSS v4 export support #45)Changes
export.ts:FORMATSarray updated, dispatch logic remappedREADME.md: Export section and interop section updated with new format names and a format reference tableVerification
--format json-tailwind→ JSON output--format css-tailwind→ CSS@themeoutput--format tailwind→ JSON output (backwards-compatible alias)check-packagepasses (24/25, pre-existing spec.md issue)