refactor(mix_winds): rename mix_tailwinds to mix_winds - #1011
Merged
Conversation
The package is published under the reserved `mix_winds` name from now on. This moves `packages/mix_tailwinds` to `packages/mix_winds`, renames the library entrypoint to `lib/mix_winds.dart`, and updates every dependency name, import, path, workflow input, publish tag pattern, melos target, and document that referenced the old name. No public API symbol changed. The `Tw*` types and the functional `div`/`span`/`button` API keep their names because they still map Tailwind CSS utilities; only the package name moves off the Tailwind trademark. The reserved `mix_winds` name already holds a `0.0.1-dev.0` placeholder release, and semver orders `0.0.1-alpha.1` below it, so the version starts at `0.1.0-alpha.0` to supersede the placeholder. References to Tailwind CSS itself (`real_tailwind/` fixtures, the Tailwind snapshots, and prose describing parity goals) are deliberately unchanged, as are the historical `mix_tailwinds` entries in released changelogs.
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
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.
Related issue
None.
Description
Publishes the package under the reserved
mix_windsname instead ofmix_tailwinds. This is a pure rename:packages/mix_tailwindsmoves topackages/mix_winds, the library entrypoint becomeslib/mix_winds.dart, and every dependency name, import, path, workflow input, publish tag pattern, melos target, and document that referenced the old name is updated.No public API symbol changed. The
Tw*types (TwParser,TwConfig,TwScope, …) and the functionaldiv/span/buttonAPI keep their names, because they still map Tailwind CSS utilities. Only the package name moves off the Tailwind trademark.Changes
packages/mix_tailwinds→packages/mix_windsandlib/mix_tailwinds.dart→lib/mix_winds.dart(plustest/tailwinds_test_helpers.dart→test/winds_test_helpers.dart).name: mix_windsandversion: 0.1.0-alpha.0. The reserved name already holds a0.0.1-dev.0placeholder release and semver orders0.0.1-alpha.1below it, so the first real release under this name has to start above0.0.1-dev.0. The pubspec records this as a comment so a later version bump doesn't regress under the placeholder.mix_winds_exampleand repointed its path dependency.publish.ymltag pattern tomix_winds-v*, thechangelog.ymlworkflow inputs (update_mix_winds,mix_winds_version), and thetest.ymlshowcase-tool working directory and npm cache path.gen:tailwinds-registry→gen:winds-registryand updated the workspace/category package lists..gitignoreshowcase path exceptions, the root/mix/mix_protocolREADMEs,AGENTS.md,llms.txt, and theskills/mixreference docs.mix-winds-visual-comparisonand the showcase source protocol id tomix-winds-showcase-source-v1, plus themixWinds*browser globals in the showcase host.Deliberately not renamed
example/real_tailwind/fixtures,example/web/tailwind-frame.*,tool/tailwind_parser_registry_snapshot.json,tool/tailwind_theme_snapshot.json,complex_tailwind_parity_test.dart, and prose describing parity goals.mix_tailwindsentries in already-released changelog sections (mix_winds0.0.1-alpha.1,mix_protocol), which record what actually shipped under the old name.Review Checklist
package:mix_tailwinds/mix_tailwinds.dartimports topackage:mix_winds/mix_winds.dart. No symbol renames.mix_windsis published to pub.dev.Validation
dart pub get(workspace) — resolved.melos run gen:build— passed; the generated parser registry, compatibility ledger, and theme data are byte-identical after the rename.melos run ci— passed across all Flutter and Dart packages, includingmix_winds/example.fvm flutter testinpackages/mix_winds— 532/532 passed.fvm dart analyzeinpackages/mix_winds— no issues.melos run analyze— schema inventory and Dart analysis passed for all 11 packages. The aggregate DCM step still reports its pre-existing issues inmix_annotationsandmix_generator; this branch has no diff in either package (git diff origin/main -- packages/mix_annotations packages/mix_generatoris empty) and DCM is disabled in CI.dart format --set-exit-if-changedover all 74 changed Dart files — 0 changed.npm testinpackages/mix_winds/tool/visual-comparison— 14/14 passed.fvm flutter build web --releaseinpackages/mix_winds/example— passed.Follow-ups (not in this PR)
mix_winds0.1.0-alpha.0via themix_winds-v*tag.mix_tailwindsdiscontinued on pub.dev, pointing atmix_winds.mix_docs_previewpackage depends on the publishedmix_winds.Additional Information (optional)
Left unmerged for human review.