deps: deduplicate npm@3 style

3 files changed, 66 insertions, 22 deletions

diff --git a/node_modules/has-unicode/LICENSE b/node_modules/has-unicode/LICENSE
index e75605296..d42e25e95 100644
--- a/node_modules/has-unicode/LICENSE
+++ b/node_modules/has-unicode/LICENSE
@@ -11,3 +11,4 @@ ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
 WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
diff --git a/node_modules/has-unicode/README.md b/node_modules/has-unicode/README.md
index 4393106fd..e9d3cc326 100644
--- a/node_modules/has-unicode/README.md
+++ b/node_modules/has-unicode/README.md
@@ -33,7 +33,8 @@ As such, we report any Windows installation as unicode capable.
 ### Unix Like Operating Systems
 
 We look at the environment variables `LC_ALL`, `LC_CTYPE`, and `LANG` in
-that order.  For `LC_ALL` and `LANG`, it looks for `.UTF-8` in the value.
+that order.  For `LC_ALL` and `LANG`, it looks for `.UTF-8` in the value. 
 For `LC_CTYPE` it looks to see if the value is `UTF-8`.  This is sufficient
 for most POSIX systems.  While locale data can be put in `/etc/locale.conf`
 as well, AFAIK it's always copied into the environment.
+
diff --git a/node_modules/has-unicode/package.json b/node_modules/has-unicode/package.json
index a56511ac6..de92acfca 100644
--- a/node_modules/has-unicode/package.json
+++ b/node_modules/has-unicode/package.json
@@ -1,36 +1,78 @@
 {
-  "name": "has-unicode",
-  "version": "1.0.0",
-  "description": "Try to guess if your terminal supports unicode",
-  "main": "index.js",
-  "scripts": {
-    "test": "tap test/*.js"
+  "_args": [
+    [
+      "has-unicode@~1.0.0",
+      "/Users/rebecca/code/npm"
+    ]
+  ],
+  "_from": "has-unicode@>=1.0.0 <1.1.0",
+  "_id": "has-unicode@1.0.0",
+  "_inCache": true,
+  "_location": "/has-unicode",
+  "_nodeVersion": "0.10.33",
+  "_npmUser": {
+    "email": "me@re-becca.org",
+    "name": "iarna"
   },
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/iarna/has-unicode"
+  "_npmVersion": "2.1.11",
+  "_phantomChildren": {},
+  "_requested": {
+    "name": "has-unicode",
+    "raw": "has-unicode@~1.0.0",
+    "rawSpec": "~1.0.0",
+    "scope": null,
+    "spec": ">=1.0.0 <1.1.0",
+    "type": "range"
   },
-  "keywords": [
-    "unicode",
-    "terminal"
+  "_requiredBy": [
+    "/",
+    "/gauge"
   ],
+  "_resolved": "https://registry.npmjs.org/has-unicode/-/has-unicode-1.0.0.tgz",
+  "_shasum": "bac5c44e064c2ffc3b8fcbd8c71afe08f9afc8cc",
+  "_shrinkwrap": null,
+  "_spec": "has-unicode@~1.0.0",
+  "_where": "/Users/rebecca/code/npm",
   "author": {
-    "name": "Rebecca Turner",
-    "email": "me@re-becca.org"
+    "email": "me@re-becca.org",
+    "name": "Rebecca Turner"
   },
-  "license": "ISC",
   "bugs": {
     "url": "https://github.com/iarna/has-unicode/issues"
   },
-  "homepage": "https://github.com/iarna/has-unicode",
+  "dependencies": {},
+  "description": "Try to guess if your terminal supports unicode",
   "devDependencies": {
     "require-inject": "^1.1.1",
     "tap": "^0.4.13"
   },
-  "readme": "has-unicode\n===========\n\nTry to guess if your terminal supports unicode\n\n```javascript\nvar hasUnicode = require(\"has-unicode\")\n\nif (hasUnicode()) {\n  // the terminal probably has unicode support\n}\n```\n```javascript\nvar hasUnicode = require(\"has-unicode\").tryHarder\nhasUnicode(function(unicodeSupported) {\n  if (unicodeSupported) {\n    // the terminal probably has unicode support\n  }\n})\n```\n\n## Detecting Unicode\n\nWhat we actually detect is UTF-8 support, as that's what Node itself supports.\nIf you have a UTF-16 locale then you won't be detected as unicode capable.\n\n### Windows\n\nSince at least Windows 7, `cmd` and `powershell` have been unicode capable.\nAs such, we report any Windows installation as unicode capable.\n\n\n### Unix Like Operating Systems\n\nWe look at the environment variables `LC_ALL`, `LC_CTYPE`, and `LANG` in\nthat order.  For `LC_ALL` and `LANG`, it looks for `.UTF-8` in the value. \nFor `LC_CTYPE` it looks to see if the value is `UTF-8`.  This is sufficient\nfor most POSIX systems.  While locale data can be put in `/etc/locale.conf`\nas well, AFAIK it's always copied into the environment.\n\n",
-  "readmeFilename": "README.md",
+  "directories": {},
+  "dist": {
+    "shasum": "bac5c44e064c2ffc3b8fcbd8c71afe08f9afc8cc",
+    "tarball": "http://registry.npmjs.org/has-unicode/-/has-unicode-1.0.0.tgz"
+  },
   "gitHead": "a8c3dcf3be5f0c8f8e26a3e7ffea7da24344a006",
-  "_id": "has-unicode@1.0.0",
-  "_shasum": "bac5c44e064c2ffc3b8fcbd8c71afe08f9afc8cc",
-  "_from": "has-unicode@*"
+  "homepage": "https://github.com/iarna/has-unicode",
+  "keywords": [
+    "terminal",
+    "unicode"
+  ],
+  "license": "ISC",
+  "main": "index.js",
+  "maintainers": [
+    {
+      "name": "iarna",
+      "email": "me@re-becca.org"
+    }
+  ],
+  "name": "has-unicode",
+  "optionalDependencies": {},
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/iarna/has-unicode"
+  },
+  "scripts": {
+    "test": "tap test/*.js"
+  },
+  "version": "1.0.0"
 }