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 🙏

© 2025 – Pkg Stats / Ryan Hefner

postcss-multiple-tailwind

v1.0.1

Published

PostCSS plugin to process multiple tailwindcss configs

Readme

PostCSS-Multiple-Tailwind

PostCSS plugin to process multiple tailwindcss configs easily.

+-- admin
|   +-- index.css
|   +-- tailwind.config.js
+-- front-end
|   +-- index.css
|   +-- tailwind.config.js
+-- postcss.config.js
+-- package.json

This allows you to have a different theme for the two css files, or have different purge settings for both. (The configurations presets are very handy to allow all your configurations to share the same base.)

Basic usage

Add @multiple-tailwind; to your input files.

@multiple-tailwind;
@tailwind base;
@tailwind components;
@tailwind utilities;

Postcss-multiple-tailwind will insert tailwindcss into the postcss process with the tailwind.config.js in the same folder as the input file.

You can also provide a different filename:

@multiple-tailwind tailwind-admin.config.js;
@tailwind base;
@tailwind components;
@tailwind utilities;

Installation

Step 1: Install plugin:

yarn add -D postcss-multiple-tailwind

Note that you also should already have postcss and tailwindcss installed.

Step 2: Add the plugin to plugins list and remove tailwindcss:

module.exports = {
  plugins: [
-   require('tailwindcss'),
+   require('postcss-multiple-tailwind'),
    require('autoprefixer')
  ]
}

Options

| Property | Type | Description | | --------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | mode | "manual", "auto" Default: "manual" | The mode determines whether @multiple-tailwind; is required in each file to be processed. When setting to auto, it is not required. | | defaultConfig | string Default: "tailwind.config.js" | The configuration file that should be used when none is specified |

This config would look something like

module.exports = {
  plugins: [
    require('postcss-multiple-tailwind')({ mode: 'auto', defaultConfig: 'my-app-styles.config.js' }),
    require('autoprefixer')
  ]
}

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/robbevp/postcss-multiple-tailwind. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.