Tailwind CSS v3.0.16 — Release Notes & Engineering Impact
Tailwind CSS v3.0.16. Source highlight: Ensure to transpile the PostCSS Nesting plugin (tailwindcss/nesting) (#7080)
238 tracked entries. Older history is imported progressively; see source coverage.
Tailwind CSS v3.0.16. Source highlight: Ensure to transpile the PostCSS Nesting plugin (tailwindcss/nesting) (#7080)
Tailwind CSS v3.0.15. Source highlight: Temporarily remove optional chaining in nesting plugin (#7077)
Tailwind CSS v3.0.14. Source highlight: Show warnings for invalid content config (#7065)
Tailwind CSS v3.0.13. Source highlight: Fix consecutive builds with at apply producing different CSS (#6999)
Tailwind CSS v3.0.12. Source highlight: Allow use of falsy values in theme config (#6917)
Tailwind CSS v3.0.11. Source highlight: Preserve casing of CSS variables added by plugins (#6888)
Tailwind CSS v3.0.10. Source highlight: Fix `@apply` in files without `@tailwind` directives (#6580, #6875)
Tailwind CSS v3.0.9. Source highlight: Improve `DEBUG` flag (#6797, #6804)
Tailwind CSS v3.0.8. Source highlight: Reduce specificity of `abbr` rule in preflight (#6671)
Tailwind CSS v3.0.7. Source highlight: Don't mutate custom color palette when overriding per-plugin colors (#6546)
Tailwind CSS v3.0.6. Source highlight: Support square bracket notation in paths (#6519)
Tailwind CSS v3.0.5. Source highlight: Revert: add `li` to list-style reset (9777562d)
Tailwind CSS v3.0.4. Source highlight: Insert always-on defaults layer in correct spot (#6526)
Tailwind CSS v3.0.3. Source highlight: Warn about invalid globs in `content` (#6449)
Tailwind CSS v3.0.2. Source highlight: Temporarily disable optimize universal defaults, fixes issue with transforms/filters/rings not being `@apply`-able in CSS modules/Svelte components/Vue components (#6461)
Tailwind CSS v3.0.1. Source highlight: Ensure complex variants with multiple classes work (#6311)
Tailwind CSS v3.0.0. Source highlight: Tailwind CSS v3.0 is here — bringing incredible performance gains, huge workflow improvements, and a seriously ridiculous number of new features.
Tailwind CSS v2.2.19. Source highlight: Ensure `corePlugins` order is consistent in AOT mode (#5928)
Tailwind CSS v2.2.18. Source highlight: Bump versions for security vulnerabilities (#5924)
Tailwind CSS v2.2.17. Source highlight: Configure chokidar's `awaitWriteFinish` setting to avoid occasional stale builds on Windows (#5758)
Tailwind CSS v2.2.16. Source highlight: JIT: Properly handle animations that use CSS custom properties (#5602)
Tailwind CSS v2.2.15. Source highlight: Ensure using CLI without `-i` for input file continues to work even though deprecated (#5464)
Tailwind CSS v2.2.14. Source highlight: Only use `@defaults` in JIT, switch back to `clean-css` in case there's any meaningful differences in the output (bf248cb)
Tailwind CSS v2.2.12. Source highlight: Ensure that divide utilities inject a default border color (#5438)
Tailwind CSS v2.2.11 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Tailwind CSS v2.2.13 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Tailwind CSS v2.2.10. Source highlight: Fix build error when using `presets: []` in config file (#4903)
Tailwind CSS v2.2.9. Source highlight: JIT: Fix `@apply`ing utilities that contain variants + the important modifier (#4854)
Tailwind CSS v2.2.8. Source highlight: Improve accessibility of default link focus styles in Firefox (#5082)
Tailwind CSS v2.2.7. Source highlight: Temporarily revert runtime performance optimizations introduced in v2.2.5, use universal selector again (#5060)
Tailwind CSS v2.2.6. Source highlight: Fix issue where base styles not generated for translate transforms in JIT (#5038)
Tailwind CSS v2.2.5. Source highlight: Added `self-baseline` utility (I know this is a patch release, no one's going to die relax) (#5000)
Tailwind CSS v2.2.4. Source highlight: Remove `postinstall` script that was preventing people from installing the library (1eacfb9)
Tailwind CSS v2.2.3. Source highlight: Pass extended color palette to theme closures so it can be used without installing Tailwind when using `npx tailwindcss` (359252c)
Tailwind CSS v2.2.2. Source highlight: JIT: Reintroduce `transform`, `filter`, and `backdrop-filter` classes purely to create stacking contexts to minimize the impact of the breaking change (#4700)
Tailwind CSS v2.2.1. Source highlight: Recover from errors gracefully in CLI watch mode (#4693)
Tailwind CSS v2.2.0. Source highlight: Six weeks ago I didn't even have v2.2 on my roadmap and yet somehow here we are today, with one of the biggest Tailwind CSS feature releases of all-time?!
Tailwind CSS v2.1.4. Source highlight: Skip `raw` PurgeCSS sources when registering template dependencies (#4542)
Tailwind CSS v2.1.3. Source highlight: Register PurgeCSS paths as PostCSS dependencies to guarantee proper cache-busting in webpack 5 (#4530)
Tailwind CSS v2.1.1. Source highlight: Fix issue where JIT engine would fail to compile when a source path isn't provided by the build runner for the current input file (#3978)
Tailwind CSS v2.1.0. Source highlight: The first new feature update since Tailwind CSS v2.0 is here and loaded with lots of cool stuff!
Tailwind CSS v2.0.4. Source highlight: Pass full `var(--bg-opacity)` value as `opacityValue` when defining colors as functions (https://github.com/tailwindlabs/tailwindcss/commit/d98f2f829d2bca83e0d14a9e2680d6859f8f4d65)
Tailwind CSS v2.0.3. Source highlight: Ensure sourcemap input is deterministic when using `@apply` in Vue components (#3356)
Tailwind CSS v2.0.2. Source highlight: Fix issue with `@apply` not working as expected with `!important` inside an at-rule (#2824)
Tailwind CSS v2.0.1. Source highlight: Nothing, just the only thing I could do when I found out npm won't let me publish the same version under two tags.
Tailwind CSS v2.0.0. Source highlight: Tailwind CSS v2.0, woohoo!
Tailwind CSS v1.9.6. Source highlight: The `presets` feature had unexpected behavior where a preset config without its own `presets` key would not extend the default config. (#2662)
Tailwind CSS v1.9.5. Source highlight: Fix issue where using `theme` with default line-heights did not resolve correctly (#2308)
Tailwind CSS v1.9.4. Source highlight: Fix issue changing plugins defined using the `withOptions` API would not trigger rebuilds in watch processes
Tailwind CSS v1.9.3. Source highlight: Fix issue where `tailwindcss init --full` scaffolded a corrupt config file (https://github.com/tailwindlabs/tailwindcss/issues/2556)