Impact Score: 5/10
Tailwind CSS v1.4.0 — Release Notes & Engineering Impact
Source available — automated, not human-reviewed
Component: tailwind · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
⚡ Executive Summary (TL;DR)
Tailwind CSS v1.4.0. Source highlight: Another new minor version so soon? Merry Coronavirus 🎄😷🎄
Who Does This Impact? (Role-Based Analysis)
💻 Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
📊 Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
⚙️ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
✨ New Features & Capabilities (3)
- New color opacity utilities
- Built-in PurgeCSS
- IE 11 target mode (experimental)
📄 View Raw Release Notes (Original Developer Log)
# Tailwind CSS v1.4.0
Another new minor version so soon? Merry Coronavirus 🎄😷🎄
## New Features
- [New color opacity utilities](#new-color-opacity-utilities)
- [Built-in PurgeCSS](#built-in-purgecss)
- [IE 11 target mode](#ie-11-target-mode) (experimental)
<a name="new-space-and-divide-layout-utilities"></a>
### New color opacity utilities (\#1627)
Tailwind v1.4 adds a new set of utilities for controlling just the alpha channel of colors:
- `bg-opacity-{value}`
- `text-opacity-{value}`
- `border-opacity-{value}`
- `divide-opacity-{value}`
- `placeholder-opacity-{value}`
These utilities compose with the existing color utilities like this:
```html
<div class="bg-red-500 bg-opacity-25">
<!-- ... -->
</div>
```
All of these new utilities inherit their values from the `opacity` config by default but can be configured independently under the following theme keys:
- `backgroundOpacity`
- `textOpacity`
- `borderOpacity`
- `placeholderOpacity`
- `divideOpacity`
Learn more in the [pull request](https://github.com/tailwindcss/tailwindcss/pull/1627).
<a name="built-in-purgecss"></a>
### Built-in PurgeCSS (\#1639)
Tailwind v1.4 adds a new `purge` option to the config for removing unused CSS without the need for configuring another tool:
```js
// tailwind.config.js
module.exports = {
purge: [
'./src/**/*.html',
'./src/**/*.vue',
'./src/**/*.jsx',
],
theme: {},
variants: {},
plugins: [],
}
```
Learn more in the [pull request](https://github.com/tailwindcss/tailwindcss/pull/1639) and the [updated "Controlling File Size" documentation](https://tailwindcss.com/docs/controlling-file-size/).
<a name="ie-11-target-mode"></a>
### IE 11 target mode (\#1635)
**This feature is experimental and may change outside of normal semantic versioning policies.**
Recently we've been adding a lot of new features to Tailwind that aren't IE 11 compatible, and if you need to support IE 11 in your projects you have to be careful not to rely on these features by mistake.
To make this easier, we've added a new `target` option to the config that lets you opt-in to a new `ie11` mode that disables any features that are not compatible with IE 11:
```js
// tailwind.config.js
module.exports = {
target: 'ie11',
theme: {},
variants: {},
plugins: [],
}
```
Learn more in the [pull request](https://github.com/tailwindcss/tailwindcss/pull/1635).