cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cordova-browser git commit: updated node modules
Date Fri, 08 May 2015 22:27:04 GMT
Repository: cordova-browser
Updated Branches:
  refs/heads/master 0a0b4e7b3 -> 06440cc29

updated node modules


Branch: refs/heads/master
Commit: 06440cc29dd97a220c31a41a42a63022252cdc69
Parents: 0a0b4e7
Author: Steve Gill <>
Authored: Fri May 8 15:26:57 2015 -0700
Committer: Steve Gill <>
Committed: Fri May 8 15:26:57 2015 -0700

 node_modules/.bin/nopt                          | 16 +-----------
 node_modules/.bin/nopt.cmd                      |  7 -----
 node_modules/.bin/shjs                          | 16 +-----------
 node_modules/.bin/shjs.cmd                      |  5 ----
 node_modules/adm-zip/package.json               | 20 ++++++++++++---
 node_modules/mime/package.json                  | 24 ++---------------
 node_modules/nopt/bin/nopt.js                   |  0
 node_modules/nopt/examples/my-program.js        |  0
 .../nopt/node_modules/abbrev/package.json       |  4 ++-
 node_modules/nopt/package.json                  | 24 ++++++++++++++---
 node_modules/shelljs/package.json               | 27 +++++++++++++++-----
 11 files changed, 66 insertions(+), 77 deletions(-)
diff --git a/node_modules/.bin/nopt b/node_modules/.bin/nopt
deleted file mode 100644
index 25995f3..0000000
--- a/node_modules/.bin/nopt
+++ /dev/null
@@ -1,15 +0,0 @@
-basedir=`dirname "$0"`
-case `uname` in
-    *CYGWIN*) basedir=`cygpath -w "$basedir"`;;
-if [ -x "$basedir/node" ]; then
-  "$basedir/node"  "$basedir/../nopt/bin/nopt.js" "$@"
-  ret=$?
-  node  "$basedir/../nopt/bin/nopt.js" "$@"
-  ret=$?
-exit $ret
diff --git a/node_modules/.bin/nopt b/node_modules/.bin/nopt
new file mode 120000
index 0000000..6b6566e
--- /dev/null
+++ b/node_modules/.bin/nopt
@@ -0,0 +1 @@
\ No newline at end of file
diff --git a/node_modules/.bin/nopt.cmd b/node_modules/.bin/nopt.cmd
deleted file mode 100644
index 1626454..0000000
--- a/node_modules/.bin/nopt.cmd
+++ /dev/null
@@ -1,7 +0,0 @@
-@IF EXIST "%~dp0\node.exe" (
-  "%~dp0\node.exe"  "%~dp0\..\nopt\bin\nopt.js" %*
-) ELSE (
-  node  "%~dp0\..\nopt\bin\nopt.js" %*
\ No newline at end of file
diff --git a/node_modules/.bin/shjs b/node_modules/.bin/shjs
index 9908675..a044997 120000
--- a/node_modules/.bin/shjs
+++ b/node_modules/.bin/shjs
@@ -1,15 +1 @@
-basedir=`dirname "$0"`
-case `uname` in
-    *CYGWIN*) basedir=`cygpath -w "$basedir"`;;
-if [ -x "$basedir/node" ]; then
-  "$basedir/node"  "$basedir/../shelljs/bin/shjs" "$@"
-  ret=$?
-  node  "$basedir/../shelljs/bin/shjs" "$@"
-  ret=$?
-exit $ret
\ No newline at end of file
diff --git a/node_modules/.bin/shjs.cmd b/node_modules/.bin/shjs.cmd
deleted file mode 100644
index 9ce460a..0000000
--- a/node_modules/.bin/shjs.cmd
+++ /dev/null
@@ -1,5 +0,0 @@
-@IF EXIST "%~dp0\node.exe" (
-  "%~dp0\node.exe"  "%~dp0\..\shelljs\bin\shjs" %*
-) ELSE (
-  node  "%~dp0\..\shelljs\bin\shjs" %*
\ No newline at end of file
diff --git a/node_modules/adm-zip/package.json b/node_modules/adm-zip/package.json
index 194b09d..35c8b7c 100644
--- a/node_modules/adm-zip/package.json
+++ b/node_modules/adm-zip/package.json
@@ -32,10 +32,24 @@
   "engines": {
     "node": ">=0.3.0"
-  "readme": "# ADM-ZIP for NodeJS\r\n\r\nADM-ZIP is a pure JavaScript implementation for
zip data compression for [NodeJS]( \r\n\r\n# Installation\r\n\r\nWith
[npm]( do:\r\n\r\n    $ npm install adm-zip\r\n\t\r\n## What is it good for?\r\nThe
library allows you to:\r\n\r\n* decompress zip files directly to disk or in memory buffers\r\n*
compress files and store them to disk in .zip format or in compressed buffers\r\n* update
content of/add new/delete files from an existing .zip\r\n\r\n# Dependencies\r\nThere are no
other nodeJS libraries that ADM-ZIP is dependent of\r\n\r\n# Examples\r\n\r\n## Basic usage\r\n```javascript\r\n\r\n\tvar
AdmZip = require('adm-zip');\r\n\r\n\t// reading archives\r\n\tvar zip = new AdmZip(\"./\");\r\n\tvar
zipEntries = zip.getEntries(); // an array of ZipEntry records\r\n\r\n\tzipEntries.forEach(function(zipEntry)
{\r\n\t    console.log(zipEntry.toString()); // outputs zip entries information\r\n\t\tif
 Entry.entryName == \"my_file.txt\") {\r\n\t\t     console.log('utf8'));
\r\n\t\t}\r\n\t});\r\n\t// outputs the content of some_folder/my_file.txt\r\n\tconsole.log(zip.readAsText(\"some_folder/my_file.txt\"));
\r\n\t// extracts the specified file to the specified location\r\n\tzip.extractEntryTo(/*entry
name*/\"some_folder/my_file.txt\", /*target path*/\"/home/me/tempfolder\", /*maintainEntryPath*/false,
/*overwrite*/true);\r\n\t// extracts everything\r\n\tzip.extractAllTo(/*target path*/\"/home/me/zipcontent/\",
/*overwrite*/true);\r\n\t\r\n\t\r\n\t// creating archives\r\n\tvar zip = new AdmZip();\r\n\t\r\n\t//
add file directly\r\n\tzip.addFile(\"test.txt\", new Buffer(\"inner content of the file\"),
\"entry comment goes here\");\r\n\t// add local file\r\n\tzip.addLocalFile(\"/home/me/some_picture.png\");\r\n\t//
get everything as a buffer\r\n\tvar willSendthis = zip.toBuffer();\r\n\t// or write everything
to disk\r\n\tzip.writeZip(/*target file name*/\"/home
 /me/\");\r\n\t\r\n\t\r\n\t// ... more examples in the wiki\r\n```\r\n\r\nFor more
detailed information please check out the [wiki](\r\n\r\n[![build
-  "readmeFilename": "",
   "_id": "adm-zip@0.4.4",
-  "_shasum": "a61ed5ae6905c3aea58b3a657d25033091052736",
+  "dist": {
+    "shasum": "a61ed5ae6905c3aea58b3a657d25033091052736",
+    "tarball": ""
+  },
   "_from": "adm-zip@0.4.4",
+  "_npmVersion": "1.3.24",
+  "_npmUser": {
+    "name": "cthackers",
+    "email": ""
+  },
+  "maintainers": [
+    {
+      "name": "cthackers",
+      "email": ""
+    }
+  ],
+  "directories": {},
+  "_shasum": "a61ed5ae6905c3aea58b3a657d25033091052736",
   "_resolved": ""
diff --git a/node_modules/mime/package.json b/node_modules/mime/package.json
index 917e6af..2bcd450 100644
--- a/node_modules/mime/package.json
+++ b/node_modules/mime/package.json
@@ -30,29 +30,9 @@
   "bugs": {
     "url": ""
+  "homepage": "",
   "_id": "mime@1.2.11",
-  "dist": {
-    "shasum": "58203eed86e3a5ef17aed2b7d9ebd47f0a60dd10",
-    "tarball": ""
-  },
-  "_from": "mime@1.2.11",
-  "_npmVersion": "1.3.6",
-  "_npmUser": {
-    "name": "broofa",
-    "email": ""
-  },
-  "maintainers": [
-    {
-      "name": "broofa",
-      "email": ""
-    },
-    {
-      "name": "bentomas",
-      "email": ""
-    }
-  ],
-  "directories": {},
   "_shasum": "58203eed86e3a5ef17aed2b7d9ebd47f0a60dd10",
   "_resolved": "",
-  "homepage": ""
+  "_from": "mime@1.2.11"
diff --git a/node_modules/nopt/bin/nopt.js b/node_modules/nopt/bin/nopt.js
old mode 100644
new mode 100755
diff --git a/node_modules/nopt/examples/my-program.js b/node_modules/nopt/examples/my-program.js
old mode 100644
new mode 100755
diff --git a/node_modules/nopt/node_modules/abbrev/package.json b/node_modules/nopt/node_modules/abbrev/package.json
index b189020..a6719dd 100644
--- a/node_modules/nopt/node_modules/abbrev/package.json
+++ b/node_modules/nopt/node_modules/abbrev/package.json
@@ -25,5 +25,7 @@
   "homepage": "",
   "_id": "abbrev@1.0.5",
-  "_from": "abbrev@1"
+  "_shasum": "5d8257bd9ebe435e698b2fa431afde4fe7b10b03",
+  "_resolved": "",
+  "_from": "abbrev@>=1.0.0 <2.0.0"
diff --git a/node_modules/nopt/package.json b/node_modules/nopt/package.json
index 24108b3..4b1f700 100644
--- a/node_modules/nopt/package.json
+++ b/node_modules/nopt/package.json
@@ -28,12 +28,30 @@
   "devDependencies": {
     "tap": "~0.4.8"
-  "readme": "If you want to write an option parser, and have it be good, there are\ntwo ways
to do it.  The Right Way, and the Wrong Way.\n\nThe Wrong Way is to sit down and write an
option parser.  We've all done\nthat.\n\nThe Right Way is to write some complex configurable
program with so many\noptions that you go half-insane just trying to manage them all, and
put\nit off with duct-tape solutions until you see exactly to the core of the\nproblem, and
finally snap and write an awesome option parser.\n\nIf you want to write an option parser,
don't write an option parser.\nWrite a package manager, or a source control system, or a service\nrestarter,
or an operating system.  You probably won't end up with a\ngood one of those, but if you don't
give up, and you are relentless and\ndiligent enough in your procrastination, you may just
end up with a very\nnice option parser.\n\n## USAGE\n\n    // my-program.js\n    var nopt
= require(\"nopt\")\n      , Stream = require(\"stream\").Strea
 m\n      , path = require(\"path\")\n      , knownOpts = { \"foo\" : [String, null]\n   
                , \"bar\" : [Stream, Number]\n                    , \"baz\" : path\n     
              , \"bloo\" : [ \"big\", \"medium\", \"small\" ]\n                    , \"flag\"
: Boolean\n                    , \"pick\" : Boolean\n                    , \"many\" : [String,
Array]\n                    }\n      , shortHands = { \"foofoo\" : [\"--foo\", \"Mr. Foo\"]\n
                    , \"b7\" : [\"--bar\", \"7\"]\n                     , \"m\" : [\"--bloo\",
\"medium\"]\n                     , \"p\" : [\"--pick\"]\n                     , \"f\" : [\"--flag\"]\n
                    }\n                 // everything is optional.\n                 // knownOpts
and shorthands default to {}\n                 // arg list defaults to process.argv\n    
            // slice defaults to 2\n      , parsed = nopt(knownOpts, shortHands, process.argv,
2)\n    console.log(parsed)\n\nThis would give you su
 pport for any of the following:\n\n```bash\n$ node my-program.js --foo \"blerp\" --no-flag\n{
\"foo\" : \"blerp\", \"flag\" : false }\n\n$ node my-program.js ---bar 7 --foo \"Mr. Hand\"
--flag\n{ bar: 7, foo: \"Mr. Hand\", flag: true }\n\n$ node my-program.js --foo \"blerp\"
-f -----p\n{ foo: \"blerp\", flag: true, pick: true }\n\n$ node my-program.js -fp --foofoo\n{
foo: \"Mr. Foo\", flag: true, pick: true }\n\n$ node my-program.js --foofoo -- -fp  # -- stops
the flag parsing.\n{ foo: \"Mr. Foo\", argv: { remain: [\"-fp\"] } }\n\n$ node my-program.js
--blatzk -fp # unknown opts are ok.\n{ blatzk: true, flag: true, pick: true }\n\n$ node my-program.js
--blatzk=1000 -fp # but you need to use = if they have a value\n{ blatzk: 1000, flag: true,
pick: true }\n\n$ node my-program.js --no-blatzk -fp # unless they start with \"no-\"\n{ blatzk:
false, flag: true, pick: true }\n\n$ node my-program.js --baz b/a/z # known paths are resolved.\n{
baz: \"/Users/isaacs/b/a/z\" }\n\n# if Array is o
 ne of the types, then it can take many\n# values, and will always be an array.  The other
types provided\n# specify what types are allowed in the list.\n\n$ node my-program.js --many
1 --many null --many foo\n{ many: [\"1\", \"null\", \"foo\"] }\n\n$ node my-program.js --many
foo\n{ many: [\"foo\"] }\n```\n\nRead the tests at the bottom of `lib/nopt.js` for more examples
of\nwhat this puppy can do.\n\n## Types\n\nThe following types are supported, and defined
on `nopt.typeDefs`\n\n* String: A normal string.  No parsing is done.\n* path: A file system
path.  Gets resolved against cwd if not absolute.\n* url: A url.  If it doesn't parse, it
isn't accepted.\n* Number: Must be numeric.\n* Date: Must parse as a date. If it does, and
`Date` is one of the options,\n  then it will return a Date object, not a string.\n* Boolean:
Must be either `true` or `false`.  If an option is a boolean,\n  then it does not need a value,
and its presence will imply `true` as\n  the value.  To negate boolea
 n flags, do `--no-whatever` or `--whatever\n  false`\n* NaN: Means that the option is strictly
not allowed.  Any value will\n  fail.\n* Stream: An object matching the \"Stream\" class in
node.  Valuable\n  for use when validating programmatically.  (npm uses this to let you\n
 supply any WriteStream on the `outfd` and `logfd` config options.)\n* Array: If `Array` is
specified as one of the types, then the value\n  will be parsed as a list of options.  This
means that multiple values\n  can be specified, and that the value will always be an array.\n\nIf
a type is an array of values not on this list, then those are\nconsidered valid values.  For
instance, in the example above, the\n`--bloo` option can only be one of `\"big\"`, `\"medium\"`,
or `\"small\"`,\nand any other value will be rejected.\n\nWhen parsing unknown fields, `\"true\"`,
`\"false\"`, and `\"null\"` will be\ninterpreted as their JavaScript equivalents.\n\nYou can
also mix types and values, or multiple types, in a list.
   For\ninstance `{ blah: [Number, null] }` would allow a value to be set to\neither a Number
or null.  When types are ordered, this implies a\npreference, and the first type that can
be used to properly interpret\nthe value will be used.\n\nTo define a new type, add it to
`nopt.typeDefs`.  Each item in that\nhash is an object with a `type` member and a `validate`
method.  The\n`type` member is an object that matches what goes in the type list.  The\n`validate`
method is a function that gets called with `validate(data,\nkey, val)`.  Validate methods
should assign `data[key]` to the valid\nvalue of `val` if it can be handled properly, or return
boolean\n`false` if it cannot.\n\nYou can also call `nopt.clean(data, types, typeDefs)` to
clean up a\nconfig object and remove its invalid properties.\n\n## Error Handling\n\nBy default,
nopt outputs a warning to standard error when invalid\noptions are found.  You can change
this behavior by assigning a method\nto `nopt.invalidHandler`.  This
  method will be called with\nthe offending `nopt.invalidHandler(key, val, types)`.\n\nIf
no `nopt.invalidHandler` is assigned, then it will console.error\nits whining.  If it is assigned
to boolean `false` then the warning is\nsuppressed.\n\n## Abbreviations\n\nYes, they are supported.
 If you define options like this:\n\n```javascript\n{ \"foolhardyelephants\" : Boolean\n,
\"pileofmonkeys\" : Boolean }\n```\n\nThen this will work:\n\n```bash\nnode program.js --foolhar
--pil\nnode program.js --no-f --pileofmon\n# etc.\n```\n\n## Shorthands\n\nShorthands are
a hash of shorter option names to a snippet of args that\nthey expand to.\n\nIf multiple one-character
shorthands are all combined, and the\ncombination does not unambiguously match any other option
or shorthand,\nthen they will be broken up into their constituent parts.  For example:\n\n```json\n{
\"s\" : [\"--loglevel\", \"silent\"]\n, \"g\" : \"--global\"\n, \"f\" : \"--force\"\n, \"p\"
: \"--parseable\"\n, \"l\" : \"--long\"\
 n}\n```\n\n```bash\nnpm ls -sgflp\n# just like doing this:\nnpm ls --loglevel silent --global
--force --long --parseable\n```\n\n## The Rest of the args\n\nThe config object returned by
nopt is given a special member called\n`argv`, which is an object with the following fields:\n\n*
`remain`: The remaining args after all the parsing has occurred.\n* `original`: The args as
they originally appeared.\n* `cooked`: The args after flags and shorthands are expanded.\n\n##
Slicing\n\nNode programs are called with more or less the exact argv as it appears\nin C land,
after the v8 and node-specific options have been plucked off.\nAs such, `argv[0]` is always
`node` and `argv[1]` is always the\nJavaScript program being run.\n\nThat's usually not very
useful to you.  So they're sliced off by\ndefault.  If you want them, then you can pass in
`0` as the last\nargument, or any other number that you'd like to slice off the start of\nthe
-  "readmeFilename": "",
+  "gitHead": "4296f7aba7847c198fea2da594f9e1bec02817ec",
   "bugs": {
     "url": ""
   "homepage": "",
   "_id": "nopt@3.0.1",
-  "_from": "nopt@~3"
+  "_shasum": "bce5c42446a3291f47622a370abbf158fbbacbfd",
+  "_from": "nopt@>=3.0.0 <4.0.0",
+  "_npmVersion": "1.4.18",
+  "_npmUser": {
+    "name": "isaacs",
+    "email": ""
+  },
+  "maintainers": [
+    {
+      "name": "isaacs",
+      "email": ""
+    }
+  ],
+  "dist": {
+    "shasum": "bce5c42446a3291f47622a370abbf158fbbacbfd",
+    "tarball": ""
+  },
+  "directories": {},
+  "_resolved": "",
+  "readme": "ERROR: No README data found!"
diff --git a/node_modules/shelljs/package.json b/node_modules/shelljs/package.json
index 56763f6..5e65061 100644
--- a/node_modules/shelljs/package.json
+++ b/node_modules/shelljs/package.json
@@ -34,13 +34,28 @@
   "engines": {
     "node": "*"
-  "readme": "# ShellJS - Unix shell commands for Node.js [![Build Status](](\n\nShellJS
is a portable **(Windows/Linux/OS X)** implementation of Unix shell commands on top of the
Node.js API. You can use it to eliminate your shell script's dependency on Unix while still
keeping its familiar and powerful commands. You can also install it globally so you can run
it from outside Node projects - say goodbye to those gnarly Bash scripts!\n\nThe project is
[unit-tested]( and battled-tested in projects like:\n\n+
[PDF.js]( - Firefox's next-gen PDF reader\n+ [Firebug](
- Firefox's infamous debugger\n+ [JSHint]( - Most popular JavaScript linter\n+
[Zepto]( - jQuery-compatible JavaScript library for modern browsers\n+
[Yeoman]( - Web application stack and d
 evelopment tool\n+ []( - Open source PaaS for quick API backend
generation\n\nand [many more](\n\n## Installing\n\nVia
npm:\n\n```bash\n$ npm install [-g] shelljs\n```\n\nIf the global option `-g` is specified,
the binary `shjs` will be installed. This makes it possible to\nrun ShellJS scripts much like
any shell script from the command line, i.e. without requiring a `node_modules` folder:\n\n```bash\n$
shjs my_script\n```\n\nYou can also just copy `shell.js` into your project's directory, and
`require()` accordingly.\n\n\n## Examples\n\n### JavaScript\n\n```javascript\nrequire('shelljs/global');\n\nif
(!which('git')) {\n  echo('Sorry, this script requires git');\n  exit(1);\n}\n\n// Copy files
to release dir\nmkdir('-p', 'out/Release');\ncp('-R', 'stuff/*', 'out/Release');\n\n// Replace
macros in each .js file\ncd('lib');\nls('*.js').forEach(function(file) {\n  sed('-i', 'BUILD_VERSION',
'v0.1.2', file);\n  se
 d('-i', /.*REMOVE_THIS_LINE.*\\n/, '', file);\n  sed('-i', /.*REPLACE_LINE_WITH_MACRO.*\\n/,
cat('macro.js'), file);\n});\ncd('..');\n\n// Run external tool synchronously\nif (exec('git
commit -am \"Auto-commit\"').code !== 0) {\n  echo('Error: Git commit failed');\n  exit(1);\n}\n```\n\n###
CoffeeScript\n\n```coffeescript\nrequire 'shelljs/global'\n\nif not which 'git'\n  echo 'Sorry,
this script requires git'\n  exit 1\n\n# Copy files to release dir\nmkdir '-p', 'out/Release'\ncp
'-R', 'stuff/*', 'out/Release'\n\n# Replace macros in each .js file\ncd 'lib'\nfor file in
ls '*.js'\n  sed '-i', 'BUILD_VERSION', 'v0.1.2', file\n  sed '-i', /.*REMOVE_THIS_LINE.*\\n/,
'', file\n  sed '-i', /.*REPLACE_LINE_WITH_MACRO.*\\n/, cat 'macro.js', file\ncd '..'\n\n#
Run external tool synchronously\nif (exec 'git commit -am \"Auto-commit\"').code != 0\n  echo
'Error: Git commit failed'\n  exit 1\n```\n\n## Global vs. Local\n\nThe example above uses
the convenience script `shelljs/global` to reduc
 e verbosity. If polluting your global namespace is not desirable, simply require `shelljs`.\n\nExample:\n\n```javascript\nvar
shell = require('shelljs');\nshell.echo('hello world');\n```\n\n## Make tool\n\nA convenience
script `shelljs/make` is also provided to mimic the behavior of a Unix Makefile. In this case
all shell objects are global, and command line arguments will cause the script to execute
only the corresponding function in the global `target` object. To avoid redundant calls, target
functions are executed only once per script.\n\nExample (CoffeeScript):\n\n```coffeescript\nrequire
'shelljs/make'\n\ntarget.all = ->\n  target.bundle()\n\n\ntarget.bundle
= ->\n  cd __dirname\n  mkdir 'build'\n  cd 'lib'\n  (cat '*.js').to '../build/output.js'\n\
= ->\n  cd __dirname\n  mkdir 'docs'\n  cd 'lib'\n  for file in ls '*.js'\n    text = grep
'//@', file     # extract special comments\n    text.replace '//@', ''      # remove comment
tags\n 'do
 cs/'\n```\n\nTo run the target `all`, call the above script without arguments:
`$ node make`. To run the target `docs`: `$ node make docs`, and so on.\n\n\n\n<!-- \n\n
reference\n\n\nAll commands run synchronously, unless otherwise stated.\n\n\n### cd('dir')\nChanges
to directory `dir` for the duration of the script\n\n### pwd()\nReturns the current directory.\n\n###
ls([options ,] path [,path ...])\n### ls([options ,] path_array)\nAvailable options:\n\n+
`-R`: recursive\n+ `-A`: all files (include files beginning with `.`, except for `.` and `..`)\n\nExamples:\n\n```javascript\nls('projs/*.js');\nls('-R',
'/users/me', '/tmp');\nls('-R', ['/users/me', '/tmp']); // same as above\n```\n\nReturns array
of files in the given path, or in current directory if no path provided.\n\n### find(path
[,path ...])\n### find(path_array)\nExamples:\n\n```javascript\nfind('src', 'lib');\nfind(['src',
 b']); // same as above\nfind('.').filter(function(file) { return file.match(/\\.js$/); });\n```\n\nReturns
array of all files (however deep) in the given paths.\n\nThe main difference from `ls('-R',
path)` is that the resulting file names\ninclude the base directories, e.g. `lib/resources/file1`
instead of just `file1`.\n\n### cp([options ,] source [,source ...], dest)\n### cp([options
,] source_array, dest)\nAvailable options:\n\n+ `-f`: force\n+ `-r, -R`: recursive\n\nExamples:\n\n```javascript\ncp('file1',
'dir1');\ncp('-Rf', '/tmp/*', '/usr/local/*', '/home/tmp');\ncp('-Rf', ['/tmp/*', '/usr/local/*'],
'/home/tmp'); // same as above\n```\n\nCopies files. The wildcard `*` is accepted.\n\n###
rm([options ,] file [, file ...])\n### rm([options ,] file_array)\nAvailable options:\n\n+
`-f`: force\n+ `-r, -R`: recursive\n\nExamples:\n\n```javascript\nrm('-rf', '/tmp/*');\nrm('some_file.txt',
'another_file.txt');\nrm(['some_file.txt', 'another_file.txt']); // same as above\n```\n\nRemo
 ves files. The wildcard `*` is accepted.\n\n### mv(source [, source ...], dest')\n### mv(source_array,
dest')\nAvailable options:\n\n+ `f`: force\n\nExamples:\n\n```javascript\nmv('-f', 'file',
'dir/');\nmv('file1', 'file2', 'dir/');\nmv(['file1', 'file2'], 'dir/'); // same as above\n```\n\nMoves
files. The wildcard `*` is accepted.\n\n### mkdir([options ,] dir [, dir ...])\n### mkdir([options
,] dir_array)\nAvailable options:\n\n+ `p`: full path (will create intermediate dirs if necessary)\n\nExamples:\n\n```javascript\nmkdir('-p',
'/tmp/a/b/c/d', '/tmp/e/f/g');\nmkdir('-p', ['/tmp/a/b/c/d', '/tmp/e/f/g']); // same as above\n```\n\nCreates
directories.\n\n### test(expression)\nAvailable expression primaries:\n\n+ `'-b', 'path'`:
true if path is a block device\n+ `'-c', 'path'`: true if path is a character device\n+ `'-d',
'path'`: true if path is a directory\n+ `'-e', 'path'`: true if path exists\n+ `'-f', 'path'`:
true if path is a regular file\n+ `'-L', 'path'`: true if path is a
  symboilc link\n+ `'-p', 'path'`: true if path is a pipe (FIFO)\n+ `'-S', 'path'`: true if
path is a socket\n\nExamples:\n\n```javascript\nif (test('-d', path)) { /* do something with
dir */ };\nif (!test('-f', path)) continue; // skip if it's a regular file\n```\n\nEvaluates
expression using the available primaries and returns corresponding value.\n\n### cat(file
[, file ...])\n### cat(file_array)\n\nExamples:\n\n```javascript\nvar str = cat('file*.txt');\nvar
str = cat('file1', 'file2');\nvar str = cat(['file1', 'file2']); // same as above\n```\n\nReturns
a string containing the given file, or a concatenated string\ncontaining the files if more
than one file is given (a new line character is\nintroduced between each file). Wildcard `*`
accepted.\n\n### 'string'.to(file)\n\nExamples:\n\n```javascript\ncat('input.txt').to('output.txt');\n```\n\nAnalogous
to the redirection operator `>` in Unix, but works with JavaScript strings (such as\nthose
returned by `cat`, `grep`, etc). _Like 
 Unix redirections, `to()` will overwrite any existing file!_\n\n### sed([options ,] search_regex,
replace_str, file)\nAvailable options:\n\n+ `-i`: Replace contents of 'file' in-place. _Note
that no backups will be created!_\n\nExamples:\n\n```javascript\nsed('-i', 'PROGRAM_VERSION',
'v0.1.3', 'source.js');\nsed(/.*DELETE_THIS_LINE.*\\n/, '', 'source.js');\n```\n\nReads an
input string from `file` and performs a JavaScript `replace()` on the input\nusing the given
search regex and replacement string. Returns the new string after replacement.\n\n### grep([options
,] regex_filter, file [, file ...])\n### grep([options ,] regex_filter, file_array)\nAvailable
options:\n\n+ `-v`: Inverse the sense of the regex and print the lines not matching the criteria.\n\nExamples:\n\n```javascript\ngrep('-v',
'GLOBAL_VARIABLE', '*.js');\ngrep('GLOBAL_VARIABLE', '*.js');\n```\n\nReads input string from
given files and returns a string containing all lines of the\nfile that match the given `regex_filt
 er`. Wildcard `*` accepted.\n\n### which(command)\n\nExamples:\n\n```javascript\nvar nodeExec
= which('node');\n```\n\nSearches for `command` in the system's PATH. On Windows looks for
`.exe`, `.cmd`, and `.bat` extensions.\nReturns string containing the absolute path to the
command.\n\n### echo(string [,string ...])\n\nExamples:\n\n```javascript\necho('hello world');\nvar
str = echo('hello world');\n```\n\nPrints string to stdout, and returns string with additional
utility methods\nlike `.to()`.\n\n### dirs([options | '+N' | '-N'])\n\nAvailable options:\n\n+
`-c`: Clears the directory stack by deleting all of the elements.\n\nArguments:\n\n+ `+N`:
Displays the Nth directory (counting from the left of the list printed by dirs when invoked
without options), starting with zero.\n+ `-N`: Displays the Nth directory (counting from the
right of the list printed by dirs when invoked without options), starting with zero.\n\nDisplay
the list of currently remembered directories. Returns an ar
 ray of paths in the stack, or a single path if +N or -N was specified.\n\nSee also: pushd,
popd\n\n### pushd([options,] [dir | '-N' | '+N'])\n\nAvailable options:\n\n+ `-n`: Suppresses
the normal change of directory when adding directories to the stack, so that only the stack
is manipulated.\n\nArguments:\n\n+ `dir`: Makes the current working directory be the top of
the stack, and then executes the equivalent of `cd dir`.\n+ `+N`: Brings the Nth directory
(counting from the left of the list printed by dirs, starting with zero) to the top of the
list by rotating the stack.\n+ `-N`: Brings the Nth directory (counting from the right of
the list printed by dirs, starting with zero) to the top of the list by rotating the stack.\n\nExamples:\n\n```javascript\n//
process.cwd() === '/usr'\npushd('/etc'); // Returns /etc /usr\npushd('+1');   // Returns /usr
/etc\n```\n\nSave the current directory on the top of the directory stack and then cd to `dir`.
With no arguments, pushd exchanges the t
 op two directories. Returns an array of paths in the stack.\n\n### popd([options,] ['-N'
| '+N'])\n\nAvailable options:\n\n+ `-n`: Suppresses the normal change of directory when removing
directories from the stack, so that only the stack is manipulated.\n\nArguments:\n\n+ `+N`:
Removes the Nth directory (counting from the left of the list printed by dirs), starting with
zero.\n+ `-N`: Removes the Nth directory (counting from the right of the list printed by dirs),
starting with zero.\n\nExamples:\n\n```javascript\necho(process.cwd()); // '/usr'\npushd('/etc');
      // '/etc /usr'\necho(process.cwd()); // '/etc'\npopd();              // '/usr'\necho(process.cwd());
// '/usr'\n```\n\nWhen no arguments are given, popd removes the top directory from the stack
and performs a cd to the new top directory. The elements are numbered from 0 starting at the
first directory listed with dirs; i.e., popd is equivalent to popd +0. Returns an array of
paths in the stack.\n\n### exit(code)\nExits t
 he current process with the given exit code.\n\n### env['VAR_NAME']\nObject containing environment
variables (both getter and setter). Shortcut to process.env.\n\n### exec(command [, options]
[, callback])\nAvailable options (all `false` by default):\n\n+ `async`: Asynchronous execution.
Defaults to true if a callback is provided.\n+ `silent`: Do not echo program output to console.\n\nExamples:\n\n```javascript\nvar
version = exec('node --version', {silent:true}).output;\n\nvar child = exec('some_long_running_process',
{async:true});\nchild.stdout.on('data', function(data) {\n  /* ... do something with data
... */\n});\n\nexec('some_long_running_process', function(code, output) {\n  console.log('Exit
code:', code);\n  console.log('Program output:', output);\n});\n```\n\nExecutes the given
`command` _synchronously_, unless otherwise specified.\nWhen in synchronous mode returns the
object `{ code:..., output:... }`, containing the program's\n`output` (stdout + stderr)  and
its exit `c
 ode`. Otherwise returns the child process object, and\nthe `callback` gets the arguments
`(code, output)`.\n\n**Note:** For long-lived processes, it's best to run `exec()` asynchronously
as\nthe current synchronous implementation uses a lot of CPU. This should be getting\nfixed
soon.\n\n### chmod(octal_mode || octal_string, file)\n### chmod(symbolic_mode, file)\n\nAvailable
options:\n\n+ `-v`: output a diagnostic for every file processed\n+ `-c`: like verbose but
report only when a change is made\n+ `-R`: change files and directories recursively\n\nExamples:\n\n```javascript\nchmod(755,
'/Users/brandon');\nchmod('755', '/Users/brandon'); // same as above \nchmod('u+x', '/Users/brandon');\n```\n\nAlters
the permissions of a file or directory by either specifying the\nabsolute permissions in octal
form or expressing the changes in symbols.\nThis command tries to mimic the POSIX behavior
as much as possible.\nNotable exceptions:\n\n+ In symbolic modes, 'a-r' and '-r' are identical.
  consideration is\n  given to the umask.\n+ There is no \"quiet\" option since default behavior
is to run silent.\n\n## Configuration\n\n\n### config.silent\nExample:\n\n```javascript\nvar
silentState = config.silent; // save old silent state\nconfig.silent = true;\n/* ... */\nconfig.silent
= silentState; // restore old silent state\n```\n\nSuppresses all command output if `true`,
except for `echo()` calls.\nDefault is `false`.\n\n### config.fatal\nExample:\n\n```javascript\nconfig.fatal
= true;\ncp('this_file_does_not_exist', '/dev/null'); // dies here\n/* more commands... */\n```\n\nIf
`true` the script will die on errors. Default is `false`.\n\n## Non-Unix commands\n\n\n###
tempdir()\nSearches and returns string containing a writeable, platform-dependent temporary
directory.\nFollows Python's [tempfile algorithm](\n\n###
error()\nTests if error occurred in the last command. Returns `null` if no error occurred,\notherw
 ise returns string explaining the error\n",
-  "readmeFilename": "",
+  "_id": "shelljs@0.1.4",
+  "dist": {
+    "shasum": "dfbbe78d56c3c0168d2fb79e10ecd1dbcb07ec0e",
+    "tarball": ""
+  },
+  "_from": "shelljs@>=0.1.4 <0.2.0",
+  "_npmVersion": "1.2.14",
+  "_npmUser": {
+    "name": "artur",
+    "email": ""
+  },
+  "maintainers": [
+    {
+      "name": "artur",
+      "email": ""
+    }
+  ],
+  "directories": {},
+  "_shasum": "dfbbe78d56c3c0168d2fb79e10ecd1dbcb07ec0e",
+  "_resolved": "",
   "bugs": {
     "url": ""
-  "_id": "shelljs@0.1.4",
-  "_shasum": "dfbbe78d56c3c0168d2fb79e10ecd1dbcb07ec0e",
-  "_from": "shelljs@^0.1.4",
-  "_resolved": ""
+  "readme": "ERROR: No README data found!"

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message