From cf9a04ca976cad4007e4f8d05257967aadccf1e9 Mon Sep 17 00:00:00 2001
From: Adam Wathan <adam.wathan@gmail.com>
Date: Fri, 8 Sep 2017 02:09:45 -0400
Subject: [PATCH] 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.
---
 package.json | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/package.json b/package.json
index a17999e96..71ccaae2a 100644
--- a/package.json
+++ b/package.json
@@ -20,7 +20,8 @@
     "watch": "nodemon -e js,css --watch src --exec 'babel-node src/build.js'",
     "test": "jest"
   },
-  "devDependencies": {
+  "devDependencies": {},
+  "dependencies": {
     "babel-cli": "^6.6.5",
     "babel-core": "^6.7.2",
     "babel-jest": "^20.0.3",
@@ -28,18 +29,16 @@
     "babel-preset-env": "^1.0.0",
     "babel-preset-react": "^6.5.0",
     "babel-preset-stage-3": "^6.24.1",
-    "jest": "^20.0.4",
-    "rimraf": "^2.6.1",
-    "stylefmt": "^6.0.0"
-  },
-  "dependencies": {
     "commander": "^2.11.0",
+    "jest": "^20.0.4",
     "lodash": "^4.17.4",
     "nodemon": "^1.11.0",
     "normalize.css": "^6.0.0",
     "postcss": "^6.0.9",
     "postcss-cssnext": "^3.0.2",
     "postcss-prettify": "^0.3.4",
+    "rimraf": "^2.6.1",
+    "stylefmt": "^6.0.0",
     "suitcss-base": "^3.0.0"
   },
   "browserslist": [