npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

vite-plugin-tailwind-legacy

v2.0.2

Published

Plugin Vite para gerar CSS Tailwind v4 compatível com navegadores antigos, utilizando PostCSS e gerando arquivo como fallback

Readme

vite-plugin-tailwind-legacy

⚡ Vite plugin that transforms Tailwind v4 CSS for legacy browser compatibility using PostCSS.

npm version License: MIT

🇺🇸 English | 🇧🇷 Versão em Português

✨ Why use it?

Problem:

  • ❌ Tailwind v4 uses modern CSS features like oklch() that break in older browsers
  • ❌ Conventional polyfills don't completely solve the problem
  • ❌ Maintaining two CSS versions manually is time-consuming

Solution:

  • ✅ Captures the CSS generated by Tailwind v4 and applies PostCSS transformations
  • ✅ Generates a new compatible CSS and injects it into build HTMLs for older browsers
  • ✅ ZERO impact on modern browsers (they load the original CSS)
  • ✅ Only legacy browsers receive the transformed CSS
  • ✅ No need to install Tailwind v3 separately

🚀 Installation

npm install --save-dev vite-plugin-tailwind-legacy@latest
# or
yarn add vite-plugin-tailwind-legacy@latest --dev

⚙️ Configuration

import { defineConfig } from 'vite'
import tailwindcss from '@tailwindcss/vite'
import TailwindLegacyPlugin from 'vite-plugin-tailwind-legacy'

export default defineConfig(({ command }) => {
  const isBuild = command === 'build'

  return {
    plugins: [
      react(),
      tailwindcss(),
      TailwindLegacyPlugin({
        assetsDir: 'dist/assets',
        publicPath: '/static/assets/',
        buildDir: 'dist',
        injectInHTML: true,
        deleteStyles: ['app', 'layout'],
        outputCSSName: 'tailwind-legacy.css',
        browserScriptName: 'browser-check.js',
      })
    ],
  }
})

🎯 What the Plugin Does

The plugin captures the CSS generated by Tailwind v4, applies PostCSS transformations, generates a new compatible CSS, and injects it into the build HTMLs for older browsers.

1. 🎨 Color Transformations

| Feature | Before (v4) | After (legacy) | |---------|------------|-----------------| | oklch() | oklch(0.65 0.15 250) | rgb(123, 104, 238) | | color-mix() | color-mix(in oklab, #1445e2 70%, #4f46e5 30%) | rgb(35, 75, 228) | | Opacity | bg-primary/50 | rgba(20, 69, 226, 0.5) | | Variables with opacity | var(--primary) / 0.5 | rgba(20, 69, 226, 0.5) |

2. 📐 Layout Transformations

| Feature | Before (v4) | After (legacy) | |---------|------------|-----------------| | space-y | .space-y-4 > *:not(:last-child) | margin-bottom: 16px | | space-x | .space-x-4 > *:not(:last-child) | margin-right: 16px | | gap | .gap-4 | margin: 8px (all sides) | | gap-x | .gap-x-4 | margin-left: 8px; margin-right: 8px | | gap-y | .gap-y-4 | margin-top: 8px; margin-bottom: 8px |

3. 🔄 CSS Transformations

/* Before (v4) */
.rotate-45 {
  rotate: 45deg;
}

/* After (legacy) */
.rotate-45 {
  transform: rotate3d(0, 0, 1, 45deg);
}
/* Before (v4) */
.scale-150 {
  scale: 1.5;
}

/* After (legacy) */
.scale-150 {
  transform: scale3d(1.5, 1.5, 1);
}
/* Before (v4) */
.translate-10 {
  translate: 10px 20px;
}

/* After (legacy) */
.translate-10 {
  transform: translate3d(10px, 20px, 0);
}

🔧 Configuration Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | assetsDir | string | 'dist/client/assets' | Output directory for assets | | publicPath | string | '/static/assets/' | Public path to load assets | | buildDir | string | 'dist' | Build output directory | | injectInHTML | boolean | true | Automatically inject script into HTML | | deleteStyles | string[] | [] | CSS patterns to remove in legacy browsers | | outputCSSName | string | 'tailwind-v3-legacy.css' | Output CSS file name | | browserScriptName | string | 'browser-check.js' | Browser check script name | | colorFormat | 'rgb' \| 'hsl' | 'rgb' | Output color format |

🔄 Browser Compatibility

| Browser | Modern (v4) | Legacy (fallback) | |---------|-------------|-------------------| | Chrome | 111+ | 87 to 110 | | Edge | 111+ | 87 to 110 | | Firefox | 128+ | 83 to 127 | | Safari | 16.4+ | 14.0 to 16.3 | | Opera | 90+ | 73 to 89 |

❓ How it Works?

1 - vite-plugin-tailwind-legacy creates a CSS file based on v3 for older browsers

2 - Adds a script to HTMLs that checks if it's an older browser. If so, it uses output.css as fallback for older browsers.

🔄 vite-plugin-tailwind-legacy Flow

graph TD
    A[Browser Accesses Page] --> B[Loads Tailwind v4 Default]
    B --> C{Is Legacy Browser?}
    C -->|NO - Modern Browser| D[Does nothing]
    C -->|YES - Legacy Browser| E[Remove Tailwind v4 Dynamically]
    E --> F[Inject Tailwind v3 CSS]

    style D fill:#005a1c,stroke:#166534
    style F fill:#005a1c,stroke:#166534
    style E fill:#c67000,stroke:#92400e

🚀 Performance

  • Zero impact on modern browsers (no extra CSS loaded)
  • Minimal impact on legacy browsers (just one additional HTTP request)
  • Generated CSS is minified for production

🤝 Contributing

Contributions are welcome! Please read our Contributing Guide.


📌 Old Version (v1)

If you need the version that used Tailwind CSS v3 separately, check the v1 documentation.

v1 used a different approach: it generated a separate CSS with Tailwind v3 for legacy browsers. v2 is faster and more efficient, transforming Tailwind v4 CSS directly with PostCSS.

We recommend using v2 for new projects.

📚 Additional Documentation