Skip to content

CHANGELOG.md

Latest commit

 

History

History
647 lines (400 loc) · 43 KB

CHANGELOG.md

File metadata and controls

647 lines (400 loc) · 43 KB

tailwindcss-patch

9.0.0

Major Changes

  • 🚀 Require modern tailwindcss-patch options and an explicit tailwindcss.version, removing support for legacy constructor aliases like cwd, tailwind, features, output, overwrite, and patch. f4d9cec by @sonofmagic

    • Workspace registry loading now rejects deprecated registry.output, registry.tailwind, and registry.patch fields. Use registry.extract, registry.tailwindcss, and registry.apply instead.
    • The default generated config now includes registry.tailwindcss.version = 4.
    • @tailwindcss-mangle/config now types only the modern registry shape. Deprecated aliases like registry.output, registry.tailwind, tailwindcss.package, tailwindcss.legacy, tailwindcss.classic, and tailwindcss.next are no longer part of the public type surface.

  • 🚀 Finalize the v9 tailwindcss-patch upgrade: 2a7f8b6 by @sonofmagic

    • require the modern TailwindcssPatcher option shape and reject legacy constructor aliases
    • require explicit tailwindcss.version and validate it against the resolved Tailwind package version
    • reject legacy workspace registry aliases such as registry.output, registry.tailwind, and registry.patch
    • default generated config to registry.tailwindcss.version = 4
    • document the v8 -> v9 migration path and modern-only configuration model

Minor Changes

  • ✨ Remove legacy public option type aliases from the v9 alpha line and keep only the modern option names such as TailwindCssPatchOptions, TailwindCssOptions, TailwindV2Options, TailwindV3Options, and TailwindV4Options. 3e1c464 by @sonofmagic

Patch Changes

  • 🐛 Downgrade cac to 6.7.14 for tailwindcss-patch to restore compatibility with CommonJS consumers that cannot load the ESM-only cac@7 package. 6adfc71 by @sonofmagic

  • 🐛 Fix Tailwind CSS v3 runtime context refresh so removed classes are dropped correctly across repeated patcher recreations, including HMR-style update flows that add and then remove content classes in the same process. 395e22f by @sonofmagic

  • 🐛 Restore automatic Tailwind CSS major version detection when registry.tailwindcss.version is omitted, while keeping strict validation for explicitly configured versions. This also removes the default config value that forced version 4 during install-time prepare scripts in Tailwind v3 demo apps. c87c9ab by @sonofmagic

  • 🐛 Fix workspace installs for monorepo consumers by making the local tailwindcss-patch entrypoint usable before dist is built. This keeps app-level prepare scripts working during fresh installs while preserving published package outputs via publishConfig. 1549b55 by @sonofmagic

  • 🐛 Preserve original runtime candidate tokens when collecting the class set for Tailwind CSS v2/v3 projects, so shorthand and full hex arbitrary color classes remain distinct and only match when the exact source token is present. ea6cbf0 by @sonofmagic

  • 🐛 Refresh parser, Tailwind, and related toolchain dependencies across the workspace, including newer runtime dependencies used by @tailwindcss-mangle/core and tailwindcss-patch. 905000b by @sonofmagic

  • 🐛 Improve tailwindcss-patch cold-start and repeated-run performance by avoiding redundant patch work, reducing unnecessary cache writes, and reusing Tailwind v4 candidate extraction state across repeated calls. Also add benchmark coverage and regression tests for cache invalidation, repeated patch/getClassSet calls, empty class sets, and v3/v4 behavior. aed889c by @sonofmagic

  • 🐛 Fix the published CommonJS runtime entry so non-CLI APIs no longer eagerly load the ESM-only cac dependency. CLI code is now split into a separate lazy-loaded bundle, which keeps require('tailwindcss-patch') working in CommonJS config loaders while preserving CLI factory support. e6b0fa3 by @sonofmagic

  • 📦 Dependencies f4d9cec → @tailwindcss-mangle/config@7.0.0

9.0.0-alpha.5

Patch Changes

  • 🐛 Preserve original runtime candidate tokens when collecting the class set for Tailwind CSS v2/v3 projects, so shorthand and full hex arbitrary color classes remain distinct and only match when the exact source token is present. ea6cbf0 by @sonofmagic

  • 🐛 Refresh parser, Tailwind, and related toolchain dependencies across the workspace, including newer runtime dependencies used by @tailwindcss-mangle/core and tailwindcss-patch. 905000b by @sonofmagic

9.0.0-alpha.4

Patch Changes

  • 🐛 Downgrade cac to 6.7.14 for tailwindcss-patch to restore compatibility with CommonJS consumers that cannot load the ESM-only cac@7 package. 6adfc71 by @sonofmagic

9.0.0-alpha.3

Patch Changes

  • 🐛 Fix the published CommonJS runtime entry so non-CLI APIs no longer eagerly load the ESM-only cac dependency. CLI code is now split into a separate lazy-loaded bundle, which keeps require('tailwindcss-patch') working in CommonJS config loaders while preserving CLI factory support. e6b0fa3 by @sonofmagic

9.0.0-alpha.2

Minor Changes

  • ✨ Remove legacy public option type aliases from the v9 alpha line and keep only the modern option names such as TailwindCssPatchOptions, TailwindCssOptions, TailwindV2Options, TailwindV3Options, and TailwindV4Options. 3e1c464 by @sonofmagic

Patch Changes

  • 📦 Dependencies 3e1c464 → @tailwindcss-mangle/config@7.0.0-alpha.2

9.0.0-alpha.1

Major Changes

  • 🚀 Require modern tailwindcss-patch options and an explicit tailwindcss.version, removing support for legacy constructor aliases like cwd, tailwind, features, output, overwrite, and patch. f4d9cec by @sonofmagic

    • Workspace registry loading now rejects deprecated registry.output, registry.tailwind, and registry.patch fields. Use registry.extract, registry.tailwindcss, and registry.apply instead.
    • The default generated config now includes registry.tailwindcss.version = 4.
    • @tailwindcss-mangle/config now types only the modern registry shape. Deprecated aliases like registry.output, registry.tailwind, tailwindcss.package, tailwindcss.legacy, tailwindcss.classic, and tailwindcss.next are no longer part of the public type surface.

  • 🚀 Finalize the v9 tailwindcss-patch upgrade: 2a7f8b6 by @sonofmagic

    • require the modern TailwindcssPatcher option shape and reject legacy constructor aliases
    • require explicit tailwindcss.version and validate it against the resolved Tailwind package version
    • reject legacy workspace registry aliases such as registry.output, registry.tailwind, and registry.patch
    • default generated config to registry.tailwindcss.version = 4
    • document the v8 -> v9 migration path and modern-only configuration model

Patch Changes

  • 🐛 Restore automatic Tailwind CSS major version detection when registry.tailwindcss.version is omitted, while keeping strict validation for explicitly configured versions. This also removes the default config value that forced version 4 during install-time prepare scripts in Tailwind v3 demo apps. c87c9ab by @sonofmagic

  • 🐛 Fix workspace installs for monorepo consumers by making the local tailwindcss-patch entrypoint usable before dist is built. This keeps app-level prepare scripts working during fresh installs while preserving published package outputs via publishConfig. 1549b55 by @sonofmagic

  • 📦 Dependencies f4d9cec → @tailwindcss-mangle/config@7.0.0-alpha.1

8.7.4-alpha.0

Patch Changes

  • 🐛 Fix Tailwind CSS v3 runtime context refresh so removed classes are dropped correctly across repeated patcher recreations, including HMR-style update flows that add and then remove content classes in the same process. 395e22f by @sonofmagic

  • 🐛 Improve tailwindcss-patch cold-start and repeated-run performance by avoiding redundant patch work, reducing unnecessary cache writes, and reusing Tailwind v4 candidate extraction state across repeated calls. Also add benchmark coverage and regression tests for cache invalidation, repeated patch/getClassSet calls, empty class sets, and v3/v4 behavior. aed889c by @sonofmagic

  • 📦 Dependencies 8937b29 → @tailwindcss-mangle/config@6.1.4-alpha.0

8.7.3

Patch Changes

  • 🐛 Fix workspace install and e2e stability when package dist artifacts are unavailable during lifecycle scripts. 84dcb16 by @sonofmagic

    • Keep published entry fields for config/shared/tailwindcss-patch pointing to dist outputs.
    • Make tw-patch install resilient in monorepo installs by avoiding eager config loading and lazily resolving config/shared modules with source fallbacks.
    • Prevent CI install failures caused by module resolution during app prepare/postinstall hooks.

  • 🐛 Refactor command-layer internals for clearer module boundaries while preserving CLI behavior. 3930935 by @sonofmagic

    • Split command internals into focused modules for context creation, metadata/definition resolution, migration argument parsing, and migration/status output rendering.
    • Strengthen module-level coverage for CLI factory wiring, command metadata/definitions, runtime/context memoization, default handler maps, migration argument normalization, and output rendering.
    • Keep public command names, options, and runtime behavior unchanged while reducing internal coupling for future maintenance.

  • 🐛 Remove legacy source-level CLI compatibility shims and standardize internal imports on src/commands/*. fdd0cf3 by @sonofmagic

    • Remove src/cli/commands.ts and src/cli/migrate-config.ts compatibility shim files.
    • Update internal tests and command wiring to import directly from src/commands/*.
    • Keep public package API and CLI behavior unchanged.

  • 📦 Dependencies 84dcb16 → @tailwindcss-mangle/config@6.1.3

8.7.2

Patch Changes

  • 🐛 upgrade @tailwindcss/node to 4.2.1 076dddd by @sonofmagic

  • 🐛 use compiler-aware transforms and stabilize workspace runtime exports a64c0da by @sonofmagic

    • route included source files to the correct AST handler by file/query language hints
    • avoid webpack html child-compilation transform conflicts and improve filter behavior
    • add app integration e2e coverage for vite/nuxt/astro/next/webpack examples
    • expose workspace package runtime entries from dist for stable next/webpack consumption

  • 📦 Dependencies a64c0da → @tailwindcss-mangle/config@6.1.2

8.7.1

Patch Changes

  • 🐛 tailwindcss-patch: add broader unit coverage for @tailwindcss/node@4.2.0 utility families, variants, fallback base loading, and @source inline() parsing. db582e3 by @sonofmagic

8.7.0

Minor Changes

  • ✨ Introduce context-aware cache governance for tailwindcss-patch with schema v2 isolation and explicit cache management APIs. 24ebd4b by @sonofmagic

    • add context fingerprint based cache isolation (cwd/config/package/options/version) to prevent cross-project cache pollution in monorepos
    • upgrade cache index schema to include schemaVersion and per-context metadata, with safe legacy fallback and lazy rebuild behavior
    • add TailwindcssPatcher#clearCache(options?) to clear current context (default) or all cache contexts with removal statistics
    • improve cache observability via debug logs that explain hit/miss reasons and mismatch details
    • harden file cache writes with lock-file coordination plus atomic temp-file rename for concurrent writers
    • add coverage for same-project hit, cross-project isolation, config/version invalidation, clearCache scopes, legacy schema handling, and concurrent writes

  • ✨ Add tw-patch migrate to automatically rewrite deprecated config keys to the modern option shape. 64820ed by @sonofmagic

    • introduce a migration engine for tailwindcss-patch.config.* and tailwindcss-mangle.config.*
    • support dry-run previews via tw-patch migrate --dry-run
    • migrate common legacy keys such as output -> extract, tailwind -> tailwindcss, overwrite -> apply.overwrite, plus nested legacy aliases
    • include migration summaries to explain per-file changes

  • ✨ Redesign TailwindcssPatcher options to a simpler, migration-friendly shape while preserving backward compatibility. a9172ef by @sonofmagic

    • add modern constructor fields:
      • projectRoot (replaces cwd)
      • tailwindcss (replaces tailwind)
      • apply (replaces overwrite + features)
      • extract (replaces output)
    • keep existing fields working, but mark legacy fields with @deprecated JSDoc and document planned removal in the next major release
    • make option normalization prefer modern fields when both modern and legacy values are provided
    • update legacy/unified config conversion and CLI overrides to emit the modern option shape

  • ✨ Add tw-patch restore command to recover configs from migration backups. 277acbd by @sonofmagic

    • introduce restore command with --report-file, --dry-run, --strict, and --json
    • add restore core API that replays backupFile entries from migration reports
    • include tests for restore success, dry-run behavior, and strict missing-backup failures

Patch Changes

  • 🐛 Improve tw-patch migrate with CI-friendly and machine-readable output modes. d93110a by @sonofmagic

    • add --check to fail when migration changes are still required
    • add --json to print structured migration reports
    • make --check run in dry-run mode automatically

  • 🐛 Add a reusable GitHub Actions template for migration report validation. c1ce57b by @sonofmagic

    • add packages/tailwindcss-patch/examples/github-actions/validate-migration-report.yml
    • document how to map validate exit codes (21/22/23/24) in CI workflows
    • link the example template from README and migration notes

  • 🐛 Improve CI template maintainability with a testable affected-shard resolver and workflow linting. 4a2f00b by @sonofmagic

    • extract affected-shard detection logic to examples/github-actions/scripts/resolve-shards.mjs
    • add unit tests covering resolver behavior and output contract
    • add .github/workflows/workflow-lint.yml to lint workflow templates and verify local template wiring

  • 🐛 Expose migration report types and publish a JSON schema. 1ed3b24 by @sonofmagic

    • export migration report helpers, constants, and related types from the package entry
    • publish tailwindcss-patch/migration-report.schema.json as a stable schema subpath
    • add tests to verify schema availability and alignment with exported constants

  • 🐛 Add a PR diff-aware GitHub Actions template for migration report validation in monorepos. fefc69a by @sonofmagic

    • add packages/tailwindcss-patch/examples/github-actions/validate-migration-report-affected.yml
    • detect affected shards from pull request file changes and only run required shards
    • add docs links in README/README-cn and migration notes

  • 🐛 Add layered validate exit codes for CI diagnostics. d143d48 by @sonofmagic

    • classify tw-patch validate failures into report incompatibility, missing backups, I/O, and unknown errors
    • expose VALIDATE_EXIT_CODES and ValidateCommandError for host integrations
    • set process exit code from validate failures in the standalone CLI entry

  • 🐛 Add migration report schema metadata and restore compatibility validation. 275c02d by @sonofmagic

    • include reportKind, schemaVersion, generatedAt, and tool metadata in tw-patch migrate reports
    • validate reportKind and schemaVersion in tw-patch restore for safer report compatibility checks
    • keep backward compatibility with legacy reports that do not include envelope metadata

  • 🐛 Publish schema for validate JSON output. 4fc6a94 by @sonofmagic

    • add tailwindcss-patch/validate-result.schema.json for tw-patch validate --json
    • include success/failure payload contracts (ok: true success and ok: false failure with reason, exitCode, message)
    • export VALIDATE_FAILURE_REASONS and align schema tests with public validate constants

  • 🐛 Refactor GitHub Actions migration-report templates to use a shared composite action. 8cc6dfe by @sonofmagic

    • add examples/github-actions/actions/validate-migration-report/action.yml
    • deduplicate migrate/validate shell logic across single, matrix, and affected templates
    • keep CI exit-code mapping (21/22/23) centralized in one reusable action

  • 🐛 Improve the affected-shards GitHub Actions template for monorepo validation. 41ecdc6 by @sonofmagic

    • add optional repo-level shard config support via .tw-patch/ci-shards.json
    • add base SHA fallback logic (merge-base) and safer run-all fallbacks when diff resolution fails
    • expand default run-all triggers for root/tooling changes
    • add ci-shards.example.json and document customization in README/MIGRATION

  • 🐛 Make tw-patch migrate file writes transactional by default. 8cfe325 by @sonofmagic

    • rollback already written migration files when a later write fails
    • improve migration error messages to include rollback status
    • add tests covering failure rollback behavior

  • 🐛 Add a matrix GitHub Actions template for monorepo migration report validation. 4070450 by @sonofmagic

    • add packages/tailwindcss-patch/examples/github-actions/validate-migration-report-matrix.yml
    • split validation into root, apps, and packages shards with per-shard artifacts
    • document single-job and matrix template choices in README and migration notes

  • 🐛 Improve the shared GitHub Actions composite action with optional environment setup controls. 8b3bf38 by @sonofmagic

    • add optional inputs to validate-migration-report action for pnpm/node setup and dependency install
    • switch single/matrix/affected workflow templates to use action-managed setup/install
    • document new action inputs in README and migration notes

  • 🐛 Improve CI documentation with copy checklists and troubleshooting guidance. b0baa22 by @sonofmagic

    • add CI copy checklists to README and README-cn covering required workflow/action/resolver files
    • add troubleshooting notes for common migration-report CI failures and local action wiring issues
    • record the documentation update in migration notes

  • 🐛 Add modern defineConfig registry support and bridge it end-to-end into tailwindcss-patch. 27c4976 by @sonofmagic

    • extend @tailwindcss-mangle/config RegistryOptions to support modern fields: projectRoot, tailwindcss, apply, extract, cache, and filter
    • keep legacy registry.output and registry.tailwind available with deprecation annotations
    • update initConfig and default registry shape to include modern extract/tailwindcss keys
    • update tailwindcss-patch unified config mapping to read both modern and legacy registry fields, preferring modern values when both are present

  • 🐛 Add a migration report validation CLI command. f69f17c by @sonofmagic

    • introduce tw-patch validate to verify migration report compatibility without restoring files
    • reuse restore dry-run checks for schema validation and backup reference scanning
    • support --report-file, --strict, and --json for validation workflows

  • 🐛 Enhance tw-patch migrate for monorepo workflows with recursive workspace scanning. cac638a by @sonofmagic

    • add --workspace to discover tailwindcss-patch.config.* and tailwindcss-mangle.config.* in sub-projects
    • add --max-depth to control recursion depth (default 6)
    • ignore common generated folders such as node_modules, .git, and dist during workspace scans

  • 🐛 Improve restore JSON observability for migration reports. 0f472ae by @sonofmagic

    • expose reportKind and reportSchemaVersion in tw-patch restore --json output when report metadata is present
    • keep compatibility with legacy reports that do not contain schema metadata
    • add unit tests for metadata and legacy restore report behavior

  • 🐛 Publish JSON schema for restore and validate outputs. 4e0ffcd by @sonofmagic

    • add tailwindcss-patch/restore-result.schema.json for tw-patch restore --json and tw-patch validate --json
    • expose the schema through package exports (source and publish configs)
    • add tests and docs to keep schema fields aligned with public report constants

  • 🐛 Add backup snapshot support for tw-patch migrate. d30bdd4 by @sonofmagic

    • introduce --backup-dir to save pre-migration file snapshots
    • include backup metadata in migration reports
    • extend tests to cover backup output paths and content

  • 🐛 Extend tw-patch migrate with scan filtering and report persistence. 487741a by @sonofmagic

    • add --include and --exclude glob filters for migration target control
    • add --report-file to persist migration JSON reports
    • keep compatibility with existing --workspace, --check, and --backup-dir flows

  • 🐛 Add a stable JSON contract for affected-shard resolver outputs and enforce it in CI. e6cdcc2 by @sonofmagic

    • add resolver JSON output mode (RESOLVE_SHARDS_OUTPUT=json) in resolve-shards.mjs
    • add resolver output schema and workflow-dispatch snapshot fixtures
    • add contract snapshot diff check in .github/workflows/workflow-lint.yml
    • extend resolver tests to cover JSON contract and snapshot alignment

  • 📦 Dependencies 27c4976 → @tailwindcss-mangle/config@6.1.1

8.6.1

Patch Changes

  • 1c0405c Thanks @sonofmagic! - Prefer CSS entry directories when resolving Tailwind v4 @config so relative configs are found even when a base directory is provided.

8.6.0

Minor Changes

  • c2fd4c1 Thanks @sonofmagic! - Add configurable cache drivers (file, memory, noop) while keeping the file cache as the default fallback.

8.5.1

Patch Changes

  • edd1171 Thanks @sonofmagic! - Gracefully skip cache updates when the cache file is locked on Windows to avoid EPERM failures.

8.5.0

Minor Changes

  • 5b11714 Thanks @sonofmagic! - Add CLI/API support for reporting which Tailwind patches are applied or pending.

8.4.3

Patch Changes

  • 0b484c1 Thanks @sonofmagic! - chore(deps): upgrade

  • 6542453 Thanks @sonofmagic! - Fix getClassSetSync() returning an empty set before Tailwind v3 contexts are ready so runtime collectors fall back to the async extraction path instead of skipping class discovery.

8.4.2

Patch Changes

  • 6bd5faa Thanks @sonofmagic! - fix cache store to write through temp files and rename atomically so concurrent patchers never read truncated JSON

8.4.1

Patch Changes

  • e5c8155 Thanks @sonofmagic! - Ensure TailwindcssPatcher uses the workspace root as the default v4 source when cssEntries point at empty folders so extract() still reports runtime classes in v4 mode.

  • 4df42ed Thanks @sonofmagic! - Stop logging cache warnings when the Tailwind class cache file is missing so repeated builds on Windows no longer show ENOENT errors.

8.4.0

Minor Changes

  • 9105a4a Thanks @sonofmagic! - expose hookable CLI command registration so host CLIs can customize command lifecycles, descriptions, and options without reimplementing tw-patch wiring

8.3.0

Minor Changes

  • 6353ff5 Thanks @sonofmagic! - Expose helpers to mount the Tailwind CSS patch CLI inside other cac apps with prefixed or renamed commands.

8.2.4

Patch Changes

  • 1af573b Thanks @sonofmagic! - Ensure Tailwind v4 CSS entries resolve @config paths relative to each CSS file when no explicit base is provided.

8.2.3

Patch Changes

  • fc73e30 Thanks @sonofmagic! - Ensure Tailwind v4 candidate extraction only keeps class names that compile to CSS so HTTP header literals like text/event-stream no longer leak into the runtime class set.

8.2.2

Patch Changes

  • Updated dependencies [6799e3b]:
    • @tailwindcss-mangle/config@6.1.0

8.2.1

Patch Changes

  • Updated dependencies [ba12f2a]:
    • @tailwindcss-mangle/config@6.0.1

8.2.0

Minor Changes

  • d516eeb Thanks @sonofmagic! - Add grouped token exports, sanitized file metadata, and CLI options for the new token reporting flow.

8.1.0

Minor Changes

  • 91f408c Thanks @sonofmagic! - Add getClassSetSync along with synchronous cache utilities so consumers that cannot await the async API can still collect Tailwind classes.

8.0.0

Major Changes

  • 0e36bfe Thanks @sonofmagic! - refactor!: redesign the patcher architecture, CLI surface, and documentation while adding Tailwind CSS v4 extraction support. Legacy APIs are wrapped for compatibility but consumers should migrate to the new entry points.

  • 18a8c3c Thanks @sonofmagic! - Adopt a unified registry/transformer configuration surface across the toolchain, update runtime consumers and tests to the new API, and refresh docs and examples to match the renamed options.

Patch Changes

  • Updated dependencies [18a8c3c]:
    • @tailwindcss-mangle/config@6.0.0

Unreleased

  • refactor: rebuild around the new TailwindcssPatcher API, explicit module boundaries (api/, patching/, runtime/, options/, extraction/).
  • feat: add Tailwind CSS v4 class discovery plus configurable output formats (json or newline delimited).
  • feat: expose helpers such as CacheStore, normalizeOptions, and v4 candidate scanners as public exports.
  • docs: add MIGRATION.md and refresh both README variants to describe the new workflow and CLI flags.

7.1.6

Patch Changes

  • 6596fae Thanks @sonofmagic! - chore(tailwindcss-patch): make @tailwindcss/node as dependencies

  • Updated dependencies [6596fae]:

    • @tailwindcss-mangle/config@5.1.2

7.1.5

Patch Changes

7.1.4

Patch Changes

7.1.3

Patch Changes

7.1.2

Patch Changes

  • b6b84f4 Thanks @sonofmagic! - chore(patch): add TailwindcssPatcher extract option

    chore(deps): upgrade

  • Updated dependencies [b6b84f4]:

    • @tailwindcss-mangle/config@5.1.1

7.1.1

Patch Changes

7.1.0

Minor Changes

Patch Changes

  • Updated dependencies [0404f90]:
    • @tailwindcss-mangle/config@5.1.0

7.0.2

Patch Changes

  • Updated dependencies [0651cae]:
    • @tailwindcss-mangle/config@5.0.6

7.0.1

Patch Changes

7.0.0

Major Changes

Patch Changes

6.0.9

Patch Changes

  • 034f9f3 Thanks @sonofmagic! - chore: bump deps and add patch only for tailwindcss v2 and v3

  • Updated dependencies [034f9f3]:

    • @tailwindcss-mangle/config@5.0.4

6.0.8

Patch Changes

6.0.7

Patch Changes

6.0.6

Patch Changes

6.0.5

Patch Changes

6.0.4

Patch Changes

  • Updated dependencies [78c0297]:
    • @tailwindcss-mangle/config@5.0.2

6.0.3

Patch Changes

6.0.2

Patch Changes

  • a8ba17e Thanks @sonofmagic! - chore: export type and add tailwindcss version config

  • Updated dependencies [a8ba17e]:

    • @tailwindcss-mangle/config@5.0.1

6.0.1

Patch Changes

  • 8e364e4 Thanks @sonofmagic! - feat!: remove getClassSet params and set default patch options

6.0.0

Major Changes

  • a3214e0 Thanks @sonofmagic! - chore: prepare for tailwindcss v4

  • 362bd49 Thanks @sonofmagic! - feat!: add tailwindcss v4 support and change getClassSet return type

    need to install @tailwindcss/node and @tailwindcss/oxide

    This is a breaking change because it changes the return type of getClassSet.

  • 4318d88 Thanks @sonofmagic! - chore: upgrade tailwindcss-config@1 and remove jiti and lilconfig dep

Patch Changes

  • Updated dependencies [362bd49]:
    • @tailwindcss-mangle/config@5.0.0

5.0.2

Patch Changes

5.0.1

Patch Changes

5.0.1-alpha.0

Patch Changes

  • a529a71 Thanks @sonofmagic! - fix: build dist empty issue

  • Updated dependencies [a529a71]:

    • @tailwindcss-mangle/config@4.0.1-alpha.0

5.0.0

Major Changes

Patch Changes

  • Updated dependencies [6879782]:
    • @tailwindcss-mangle/config@4.0.0

5.0.0-alpha.0

Major Changes

Patch Changes

  • Updated dependencies [6879782]:
    • @tailwindcss-mangle/config@4.0.0-alpha.0

3.0.1

Patch Changes

  • 3c2d2b9: fix(tailwindcss-patch): monorepo basedir option

3.0.0

Major Changes

  • 3e7d646: support tailwindcss@2 postcss7 compat

2.2.4

Patch Changes

  • eb9d5e9 Thanks @sonofmagic! - fix: "npx tw-patch extract" does not look for all valid Tailwind config file paths #57

2.2.3

Patch Changes