No description
Find a file
Adam Wathan cf9a04ca97 Move dev dependencies to dependencies
Installing NPM packages from GitHub means we don't have the benefit
of NPM running our babel/prepare scripts on publish.

When you try to install Tailwind, it'll blow up because it tries to
run the prepare script on install and none of the dev dependencies
are installed.

There may be a better way to handle this but there is zero fucking
information on the internet about what a "proper" private package
development workflow looks like, especially when you have a build
step.
2017-09-08 02:09:45 -04:00
__tests__ Add support for merging and replacing config keys from a single config file 2017-09-02 07:41:55 -04:00
dist Add basic set of opacity utilities 2017-09-03 18:26:59 -04:00
docs Add basic set of opacity utilities 2017-09-03 18:26:59 -04:00
src Clean up formatting 2017-09-06 09:35:18 -04:00
.editorconfig Convert new stuff to use ES6 modules 2017-08-27 18:02:41 -04:00
.gitignore Ignore example folder I use to test the CLI 2017-08-28 15:01:31 -05:00
package-lock.json Apparently supposed to commit this 2017-08-28 15:01:20 -05:00
package.json Move dev dependencies to dependencies 2017-09-08 02:09:45 -04:00
README.md Init 2017-07-20 08:39:57 -04:00
tailwindcss.sublime-project Add a sublime project file to hide /lib from searches 2017-08-27 18:02:41 -04:00

TailwindCSS

A utility-first CSS framework for rapid UI development.