Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

tailwindcss-export-config

Package Overview
Dependencies
Maintainers
1
Versions
23
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

tailwindcss-export-config

Export Tailwindcss config options to SASS, SCSS, LESS and Stylus

  • 2.0.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
684
decreased by-12.2%
Maintainers
1
Weekly downloads
 
Created
Source

Tailwindcss-export-config

Export Tailwind config options like a pro

Notice

This branch works with v1.x of Tailwindcss. If you are using the older 0.x version, please use the master branch.

Features

  • :rocket: Exports Tailwindcss config options to SASS, SCSS, LESS and Stylus.
  • :boom: CLI and Node api support
  • :muscle: Unit Tested

Getting started

  1. Using npm: npm install tailwindcss-export-config

or with yarn:

yarn add tailwindcss-export-config

  1. Make a package.json script and run it for convenience
{
  "scripts": {
    "export-tailwind-config": "tailwindcss-export-config --config=src/styles/tailwind/tailwind.config.js --destination=src/styles/scss/tailwind-configs --format=scss"
  }
}

or import inside your own node script

import TailwindExportConfig from 'tailwindcss-export-config'
const converter = new TailwindExportConfig({
  config: 'path/to/tailwind.config.js',
  destination: 'converted/file/destination',
  format: 'scss',
  prefix: 'tw',
  flat: true
})
// writeToFile returns a promise so we can chain off it
converter.writeToFile().then(() => {
  console.log('Success')
}).catch((error) => {
  console.log('Oops', error.message)
})

Config Options

All options are available to the CLI and node package. Type tailwindcss-export-config --h for help.

PropTypeRequiredDescription
configString,ObjecttrueTailwindcss config path or config object to transform
destinationStringtrueDestination to save converted file
formatStringtrueThe format in which to convert the file
prefixStringfalseAn optional prefix for each variable name
flatBooleanfalseOptionally transforms the variables from nested maps to flat level variables. Less does not support nested maps so we default to flat for them always.

Example export

Lets get a portion of the Tailwind config

module.exports = {
  colors: {
    'transparent': 'transparent',
    'black': '#22292f',
    'grey-darkest': '#3d4852',
    'grey-darker': '#606f7b',
    'grey-dark': '#8795a1',
    'grey': '#b8c2cc',
    'grey-light': '#dae1e7',
    'grey-lighter': '#f1f5f8',
    'grey-lightest': '#f8fafc',
    'white': '#ffffff',
  }
}

How would this look in the various preprocessors? Whats does the flat param do?

SCSS

Using the flat param we get:

$colors-transparent: transparent;
$colors-black: #22292f;
$colors-grey-darkest: #3d4852;
$colors-grey-darker: #606f7b;
$colors-grey-dark: #8795a1;
$colors-grey: #b8c2cc;
$colors-grey-light: #dae1e7;
$colors-grey-lighter: #f1f5f8;
$colors-grey-lightest: #f8fafc;
$colors-white: #ffffff;

or without with the flat param set to false

$colors: (
  transparent: transparent,
  black: #22292f,
  grey-darkest: #3d4852,
  grey-darker: #606f7b,
  grey-dark: #8795a1,
  grey: #b8c2cc,
  grey-light: #dae1e7,
  grey-lighter: #f1f5f8,
  grey-lightest: #f8fafc,
  white: #ffffff
);

The second (nested map) approach is a bit more annoying to work with as you have to do map_get($colors, black) but things are easier to loop if you need to.

Sass is almost the same and you can import both sass and scss vars into the same project. We support them both if someone prefers one syntax over the other.

LESS

@colors-transparent: transparent;
@colors-black: #22292f;
@colors-grey-darkest: #3d4852;
@colors-grey-darker: #606f7b;
@colors-grey-dark: #8795a1;
@colors-grey: #b8c2cc;
@colors-grey-light: #dae1e7;
@colors-grey-lighter: #f1f5f8;
@colors-grey-lightest: #f8fafc;
@colors-white: #ffffff;

Less does not have nested maps so passing the flat param will not do anything

Stylus

$colors-transparent = transparent
$colors-black = #22292f
$colors-grey-darkest = #3d4852
$colors-grey-darker = #606f7b
$colors-grey-dark = #8795a1
$colors-grey = #b8c2cc
$colors-grey-light = #dae1e7
$colors-grey-lighter = #f1f5f8
$colors-grey-lightest = #f8fafc
$colors-white = #ffffff

or with the flat param to false

$colors = {
  transparent: transparent,
  black: #22292f,
  grey-darkest: #3d4852,
  grey-darker: #606f7b,
  grey-dark: #8795a1,
  grey: #b8c2cc,
  grey-light: #dae1e7,
  grey-lighter: #f1f5f8,
  grey-lightest: #f8fafc,
  white: #ffffff
}

Using the colors is a matter of reaching using dot notation $colors.black or $colors[black].

Prefix

You can prefix the colors to escape naming collisions by using the prefix param

--prefix=tw

$tw-colors-transparent: transparent;
$tw-colors-black: #22292f;
$tw-colors-grey-darkest: #3d4852;
$tw-colors-grey-darker: #606f7b;
$tw-colors-grey-dark: #8795a1;
$tw-colors-grey: #b8c2cc;
$tw-colors-grey-light: #dae1e7;
$tw-colors-grey-lighter: #f1f5f8;
$tw-colors-grey-lightest: #f8fafc;
$tw-colors-white: #ffffff;

Keywords

FAQs

Package last updated on 29 Aug 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc