v4.0.1

Patch Changes

• Handle number theme values (#261)

  Internal utilities assumed theme values would always be string typed, but in some cases they may be numbers.

• Handle anomalous values from Tailwind language server (#263)

v4.0.0

Major Changes

• Update plugin for Tailwind v4 support (#247)

  v4 was a major change to how projects are configured as well as what plugins are allowed to modify. Previously, this plugin disabled corePlugins like fontSize in order to include custom CSS properties within the same utilities. This is no longer possible in v4, so while the usage hasn't changed, the CSS being output now includes duplicate declarations — one from the plugin and one from Tailwind itself.

  v4 also allows configuration within CSS itself. However, this plugin relies on object values which aren't supported in CSS, so a JavaScript config file is still required. You can either use the JS file for all your settings, or just the settings for this plugin and configure the rest of your project in CSS.

  The mode option has also been removed. This also removes the dependency on @capsizecss/core.

v3.0.5

Patch Changes

• Reworked internals (#214)
  No notable change in CSS output. Should support Tailwind TypeScript configs better now.

v3.0.4

Patch Changes

• Fix fontSize utility not including default fontWeight settings #209

v3.0.3

Patch Changes

• Fix precision loss with fractional pixel font-sizes #178

  Thanks @andriytyurnikov!

v3.0.2

🐛 Fixed

• Use correct custom property with default lineHeight values #153

  Fixes issue with a leading-* class being required even with fontSize values including a default lineHeight.

v3.0.1

🐛 Fixed

• Remove unit from --font-size-px custom property #128

  Thanks @essejmclean!
  Fixes issue with calc() functions not working correctly.

v3.0.0

💣 Breaking Changes

• Add modern output mode #123

  In this mode the fontFamily, fontSize, and lineHeight core plugins are replaced, adding custom properties to the output of each which are used in the calc() expressions in the utility class.

  modern mode is enabled by default. The previous functionality can be maintained if needed by switching to classic mode.

v2.1.0

🎁 Added

• Allow custom activation class via new className option #103

  require('tailwindcss-capsize')({ className: 'leading-trim' })

v2.0.0

💣 Breaking Changes

• Use new @capsize/core library #94 Thanks @DylanVann!
  This will change the final output CSS, as the technique to perform
  the leading trim has been simplified. See the capsize release notes
  for more details.

🐛 Fixed

• Fix usage when requireing plugin #95 Thanks @DylanVann!

  - require('tailwindcss-capsize').default
  + require('tailwindcss-capsize')