@tailwindcss-mangle/config@7.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.

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

• 🐛 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

• 🐛 Refresh internal dependency ranges for the published config and core packages, including fs-extra, postcss, @vue/compiler-sfc, and svelte, to keep the workspace aligned with the updated toolchain. 8937b29 by @sonofmagic

• 🐛 Align workspace package metadata with built dist outputs and fix config consumption to use the modern registry.extract.file fallback. Demo apps now declare the workspace packages they execute or import so Turbo can derive internal build dependencies correctly. b42175f by @sonofmagic

• 📦 Dependencies b42175f
  → @tailwindcss-mangle/shared@4.1.4