1.0.1 • Published 2 years ago

postcss-multiple-tailwind v1.0.1

Weekly downloads
-
License
MIT
Repository
github
Last release
2 years ago

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

PropertyTypeDescription
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.
defaultConfigstring 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.