Tailwindcss Theming Versions Save

CSS-variables-based swappable themes for Tailwind CSS

v2.2.1

4 years ago
  • Fixed an issue where color variants' opacity was duplicated (output as 0,0,0,.5,.5 instead of 0,0,0,.5).

v2.2.0

4 years ago
  • Added the possibility to extend Tailwind configuration with custom CSS properties
    • Syntax is .variable('name', 'value', 'tailwindConfigurationItem')
  • New documentation

v2.1.0

4 years ago

Example

The following theme configuration:

new Theme()
  .color('primary', 'white')
  .variable('theme-scheme', 'light')
  .variable('font-title', ['Roboto', '"Segoe UI"', 'Arial']);

Will generate:

:root {
  --color-primary: #ffffff;
  --theme-scheme: light;
  --font-title: Roboto,"Segoe UI",Arial;
}

v2.0.2

4 years ago
  • Fixed an issue with color variants.
    • Can be a breaking change: before, opacity was not taking into account (eg. #ffffff00 would be white)
    • Now, opacity is taking into account (eg. #ffffff00 will be transparent)

Note: v2.0.1 actually contains these changes, but v2.0.2 fixes a typo in them.

2.0.0

4 years ago
  • Configuration changes
    • A theme is no longer default by default, you have to call .default()
    • ThemeBuilder is now more fluent
  • Added .dark() and .light() helpers in ThemeBuilder
  • Removed .schemeDefault(), replaced by existing .default()
  • Removed .keep(), replaced by .assignable()

v1.0.0-canary-2

4 years ago
  • Fixed an issue with opacity variants being parsed as pixel values by Tailwind.

v1.0.0-canary-1

4 years ago
  • Fixed an issue where default colors which had variants were not generated.

v1.0.0-canary

4 years ago
  • Update for tailwindcss@canary.
  • Contains breaking API changes, check the readme for the new configuration instructions.