cssesc-source 0.1.0 → 1.0.1

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/MIT-LICENSE.txt

@@ -1,21 +0,0 @@
-Copyright (c) 2012 
-
-Filirom1
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/README.md

@@ -1,43 +0,0 @@
-# StripColorCodes
-
-When using libs like [colors](https://github.com/marak/colors.js/) your
-shell is beautifull but if you store the result in a file, it's not so
-good :-/
-
-    $ vim myLog
-    
-    20120413045946 ^[[34mdebug:  ^[[39m […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode·
-    20120413045946 ^[[34mdebug:  ^[[39m […n/my-service] my-service started.·
-
-
-You have all those ugly codes `^[[34m` everywhere in your logs.
-
-
-STOP worring about this, use StripColorCodes !
-
-    $ npm install -g stripcolorcodes
-
-You can use it with unix pipe:
-
-    $ cat /root/.forever/T9ZW.log | stripcolorcodes
-    20120413045946 debug:   […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode
-    20120413045946 debug:   […n/my-service] my-service started.
-
-Or with a file:
-
-    $ stripcolorcodes /root/.forever/T9ZW.log
-    20120413045946 debug:   […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode
-    20120413045946 debug:   […n/my-service] my-service started.
-
-Or programmatically:
-
-    var stripColorCodes = require('stripcolorcodes');
-
-    fs.readFile(file, function(err, data){
-      if(err) return console.error(err);
-      process.stdout.write(stripcolorcodes(data.toString()));
-    });
-
-Enjoy !
-
-### LICENCE MIT

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/bin/stripcolorcodes.js

@@ -1,18 +0,0 @@
-#!/usr/bin/env node
-var stripcolorcodes = require('..'),
-  fs = require('fs');
-
-if(process.argv.length <= 2) {
-  //pipe sdtin
-  process.stdin.resume();
-  process.stdin.setEncoding('utf8');
-
-  process.stdin.on('data', function (chunk) {
-    process.stdout.write(stripcolorcodes(chunk));
-  });
-}else{
-  fs.readFile(process.argv[2], function(err, data){
-    if(err) return console.error(err);
-    process.stdout.write(stripcolorcodes(data.toString()));
-  })
-}

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/index.js

@@ -1,3 +0,0 @@
-module.exports = function stripcolorcodes(strWithColors){
-  return strWithColors.replace(/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]/g, '');
-}

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/package.json

@@ -1,42 +0,0 @@
-{
-  "author": {
-    "name": "Filirom1",
-    "email": "filirom1@gmail.com"
-  },
-  "name": "stripcolorcodes",
-  "description": "Remove color codes (special characters) with nodejs",
-  "version": "0.1.0",
-  "repository": {
-    "type": "git",
-    "url": "git@github.com/Filirom1/stripcolorcodes.git"
-  },
-  "main": "index.js",
-  "bin": {
-    "stripcolorcodes": "bin/stripcolorcodes.js"
-  },
-  "licenses": [
-    {
-      "type": "MIT",
-      "url": "http://www.opensource.org/licenses/MIT"
-    }
-  ],
-  "dependencies": {},
-  "devDependencies": {
-    "vows": "~0.6.2"
-  },
-  "optionalDependencies": {},
-  "engines": {
-    "node": "*"
-  },
-  "scripts": {
-    "test": "./node_modules/.bin/vows test/*.js --spec"
-  },
-  "readme": "# StripColorCodes\n\nWhen using libs like [colors](https://github.com/marak/colors.js/) your\nshell is beautifull but if you store the result in a file, it's not so\ngood :-/\n\n    $ vim myLog\n    \n    20120413045946 ^[[34mdebug:  ^[[39m […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode·\n    20120413045946 ^[[34mdebug:  ^[[39m […n/my-service] my-service started.·\n\n\nYou have all those ugly codes `^[[34m` everywhere in your logs.\n\n\nSTOP worring about this, use StripColorCodes !\n\n    $ npm install -g stripcolorcodes\n\nYou can use it with unix pipe:\n\n    $ cat /root/.forever/T9ZW.log | stripcolorcodes\n    20120413045946 debug:   […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode\n    20120413045946 debug:   […n/my-service] my-service started.\n\nOr with a file:\n\n    $ stripcolorcodes /root/.forever/T9ZW.log\n    20120413045946 debug:   […n/my-service] Starting my-service on 0.0.0.0:8080 in dev mode\n    20120413045946 debug:   […n/my-service] my-service started.\n\nOr programmatically:\n\n    var stripColorCodes = require('stripcolorcodes');\n\n    fs.readFile(file, function(err, data){\n      if(err) return console.error(err);\n      process.stdout.write(stripcolorcodes(data.toString()));\n    });\n\nEnjoy !\n\n### LICENCE MIT\n",
-  "readmeFilename": "README.md",
-  "bugs": {
-    "url": "https://github.com/Filirom1/stripcolorcodes/issues"
-  },
-  "homepage": "https://github.com/Filirom1/stripcolorcodes",
-  "_id": "stripcolorcodes@0.1.0",
-  "_from": "stripcolorcodes@~0.1.0"
-}

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/test/fixture/with-colors

@@ -1,2 +0,0 @@
-20120413045946 debug:   […n/smart-admin-front] Starting smart-admin-front on 0.0.0.0:8080 in dev mode 
-20120413045946 debug:   […n/smart-admin-front] Smart-admin-front started. 

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/test/fixture/without-colors

@@ -1,2 +0,0 @@
-20120413045946 debug:   […n/smart-admin-front] Starting smart-admin-front on 0.0.0.0:8080 in dev mode 
-20120413045946 debug:   […n/smart-admin-front] Smart-admin-front started. 

data/vendor/node_modules/grunt-shell/node_modules/stripcolorcodes/test/stripcolorcodes-test.js

@@ -1,20 +0,0 @@
-var vows = require('vows'),
-  assert = require('assert'),
-  fs = require('fs'),
-  stripColorCodes = require('..');
-
-vows.describe('Srtip color codes').addBatch({
-  'Given a colorized string': {
-    topic: fs.readFileSync(__dirname + '/fixture/with-colors').toString(),
-
-    'When stripping colors': {
-      topic: function(strWithColors){
-        return stripColorCodes(strWithColors);
-      },
-
-      'Then the string should not contain any color code': function(withoutColor){
-        assert.equal(withoutColor, fs.readFileSync(__dirname + '/fixture/without-colors').toString());
-      }
-    }
-  }
-}).exportTo(module);

data/vendor/node_modules/grunt-shell/package.json

@@ -1,53 +0,0 @@
-{
-  "name": "grunt-shell",
-  "version": "0.3.1",
-  "description": "Run shell commands",
-  "keywords": [
-    "gruntplugin",
-    "shell",
-    "command",
-    "cmd",
-    "exec",
-    "spawn",
-    "process",
-    "cli"
-  ],
-  "homepage": "https://github.com/sindresorhus/grunt-shell",
-  "bugs": {
-    "url": "https://github.com/sindresorhus/grunt-shell/issues"
-  },
-  "author": {
-    "name": "Sindre Sorhus",
-    "email": "sindresorhus@gmail.com",
-    "url": "http://sindresorhus.com"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git://github.com/sindresorhus/grunt-shell.git"
-  },
-  "scripts": {
-    "test": "grunt"
-  },
-  "dependencies": {
-    "stripcolorcodes": "~0.1.0"
-  },
-  "devDependencies": {
-    "grunt": "~0.4.0"
-  },
-  "peerDependencies": {
-    "grunt": "~0.4.0"
-  },
-  "engines": {
-    "node": ">=0.8.0"
-  },
-  "licenses": {
-    "type": "MIT"
-  },
-  "files": [
-    "tasks/shell.js"
-  ],
-  "readme": "# grunt-shell\n\n*Requires grunt 0.4. Use version 0.1.4 for grunt 0.3 compatibility*\n\n[Grunt][grunt] task to run shell commands.\n\nA good way to interact with other CLI tools. E.g. compiling Compass `compass compile` or get the current git branch `git branch`.\n\n\n## Getting Started\n\nIf you haven't used [grunt][] before, be sure to check out the [Getting Started][] guide, as it explains how to create a [gruntfile][Getting Started] as well as install and use grunt plugins. Once you're familiar with that process, install this plugin with this command:\n\n```shell\nnpm install --save-dev grunt-shell\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-shell');\n```\n\n[grunt]: http://gruntjs.com\n[Getting Started]: https://github.com/gruntjs/grunt/wiki/Getting-started\n\n\n## Documentation\n\n\n### Example usage\n\n\n#### Run command\n\nCreate a folder named `test`.\n\n```javascript\nshell: {\n\tmakeDir: {\n\t\tcommand: 'mkdir test'\n\t}\n}\n```\n\nThe `command` property supports templates:\n\n```javascript\ntestDir: 'test',\nshell: {\n\tmakeDir: {\n\t\tcommand: 'mkdir <%= testDir %>'\n\t}\n}\n```\n\nYou can also supply a function that returns the command:\n\n```javascript\nshell: {\n\tmakeDir: {\n\t\tcommand: function () {\n\t\t\treturn 'echo hello';\n\t\t}\n\t}\n}\n```\n\n\n#### Run command and display the output\n\nOutput a directory listing in your Terminal.\n\n```javascript\nshell: {\n\tdirListing: {\n\t\tcommand: 'ls',\n\t\toptions: {\n\t\t\tstdout: true\n\t\t}\n\t}\n}\n```\n\n\n#### Custom callback\n\nDo whatever you want with the output.\n\n```javascript\nfunction log(err, stdout, stderr, cb) {\n\tconsole.log(stdout);\n\tcb();\n}\n\n...\n\nshell: {\n\tdirListing: {\n\t\tcommand: 'ls',\n\t\toptions: {\n\t\t\tcallback: log\n\t\t}\n\t}\n}\n```\n\n\n#### Option passed to the .exec() method\n\nRun a command in another directory. In this example we run it in a subfolder using the `cwd` (current working directory) option.\n\n```javascript\nshell: {\n\tsubfolderLs: {\n\t\tcommand: 'ls',\n\t\toptions: {\n\t\t\tstdout: true,\n\t\t\texecOptions: {\n\t\t\t\tcwd: 'tasks'\n\t\t\t}\n\t\t}\n\t}\n}\n```\n\n\n#### Multiple commands\n\nRun multiple commands by placing them in an array which is joined using `&&` or `;`. `&&` means run this only if the previous command succeded. You can also use `&` to have the commands run concurrently (by executing all commands except the last one in a subshell).\n\n```javascript\nshell: {\n\tmultiple: {\n\t\tcommand: [\n\t\t\t'mkdir test',\n\t\t\t'cd test',\n\t\t\t'ls'\n\t\t].join('&&')\n\t}\n}\n```\n\n\n### Config\n\n\n#### command\n\n**Required**  \nType: `String|Function`\n\nThe command you want to run or a function which returns it. Supports underscore templates.\n\n\n### Options\n\n\n#### stdout\n\nDefault: `false`  \nType: `Boolean`\n\nShow stdout in the Terminal.\n\n\n#### stderr\n\nDefault: `false`  \nType: `Boolean`\n\nShow stderr in the Terminal.\n\n\n#### failOnError\n\nDefault: `false`  \nType: `Boolean`\n\nFail task if it encounters an error. Does not apply if you specify a `callback`.\n\n\n#### callback(err, stdout, stderr, cb)\n\nDefault: `function () {}`  \nType: `Function`\n\nLets you override the default callback with your own.\n\n**Make sure to call the `cb` method when you're done.**\n\n\n#### execOptions\n\nDefault: `undefined`  \nAccepts: Object\n\nSpecify some options to be passed to the [.exec()](http://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback) method:\n\n- `cwd` String *Current working directory of the child process*\n- `env` Object *Environment key-value pairs*\n- `setsid` Boolean\n- `encoding` String *(Default: 'utf8')*\n- `timeout` Number *(Default: 0)*\n- `maxBuffer` Number *(Default: 200\\*1024)*\n- `killSignal` String *(Default: 'SIGTERM')*\n\n\n## Upgrade from 0.1.4 to 0.2.0\n\nBecause of the transition to grunt 0.4 there are some changes. To conform to new grunt standards, all options are now to be specified in an `options` object. I also took the opportunity to improve the task. The `stdout` and `stderr` options now only supports a boolean. If you want to do something with the result use the `callback` option. The `callback` option also changed.\n\n\n## Tests\n\nGrunt currently doesn't have a way to test tasks directly. You can test this task by running `grunt` and manually verify that it works.\n\n\n## License\n\nMIT License • © [Sindre Sorhus](http://sindresorhus.com)\n",
-  "readmeFilename": "readme.md",
-  "_id": "grunt-shell@0.3.1",
-  "_from": "grunt-shell@~0.3.1"
-}

data/vendor/node_modules/grunt-shell/readme.md

@@ -1,221 +0,0 @@
-# grunt-shell
-
-*Requires grunt 0.4. Use version 0.1.4 for grunt 0.3 compatibility*
-
-[Grunt][grunt] task to run shell commands.
-
-A good way to interact with other CLI tools. E.g. compiling Compass `compass compile` or get the current git branch `git branch`.
-
-
-## Getting Started
-
-If you haven't used [grunt][] before, be sure to check out the [Getting Started][] guide, as it explains how to create a [gruntfile][Getting Started] as well as install and use grunt plugins. Once you're familiar with that process, install this plugin with this command:
-
-```shell
-npm install --save-dev grunt-shell
-```
-
-Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
-
-```js
-grunt.loadNpmTasks('grunt-shell');
-```
-
-[grunt]: http://gruntjs.com
-[Getting Started]: https://github.com/gruntjs/grunt/wiki/Getting-started
-
-
-## Documentation
-
-
-### Example usage
-
-
-#### Run command
-
-Create a folder named `test`.
-
-```javascript
-shell: {
-	makeDir: {
-		command: 'mkdir test'
-	}
-}
-```
-
-The `command` property supports templates:
-
-```javascript
-testDir: 'test',
-shell: {
-	makeDir: {
-		command: 'mkdir <%= testDir %>'
-	}
-}
-```
-
-You can also supply a function that returns the command:
-
-```javascript
-shell: {
-	makeDir: {
-		command: function () {
-			return 'echo hello';
-		}
-	}
-}
-```
-
-
-#### Run command and display the output
-
-Output a directory listing in your Terminal.
-
-```javascript
-shell: {
-	dirListing: {
-		command: 'ls',
-		options: {
-			stdout: true
-		}
-	}
-}
-```
-
-
-#### Custom callback
-
-Do whatever you want with the output.
-
-```javascript
-function log(err, stdout, stderr, cb) {
-	console.log(stdout);
-	cb();
-}
-
-...
-
-shell: {
-	dirListing: {
-		command: 'ls',
-		options: {
-			callback: log
-		}
-	}
-}
-```
-
-
-#### Option passed to the .exec() method
-
-Run a command in another directory. In this example we run it in a subfolder using the `cwd` (current working directory) option.
-
-```javascript
-shell: {
-	subfolderLs: {
-		command: 'ls',
-		options: {
-			stdout: true,
-			execOptions: {
-				cwd: 'tasks'
-			}
-		}
-	}
-}
-```
-
-
-#### Multiple commands
-
-Run multiple commands by placing them in an array which is joined using `&&` or `;`. `&&` means run this only if the previous command succeded. You can also use `&` to have the commands run concurrently (by executing all commands except the last one in a subshell).
-
-```javascript
-shell: {
-	multiple: {
-		command: [
-			'mkdir test',
-			'cd test',
-			'ls'
-		].join('&&')
-	}
-}
-```
-
-
-### Config
-
-
-#### command
-
-**Required**  
-Type: `String|Function`
-
-The command you want to run or a function which returns it. Supports underscore templates.
-
-
-### Options
-
-
-#### stdout
-
-Default: `false`  
-Type: `Boolean`
-
-Show stdout in the Terminal.
-
-
-#### stderr
-
-Default: `false`  
-Type: `Boolean`
-
-Show stderr in the Terminal.
-
-
-#### failOnError
-
-Default: `false`  
-Type: `Boolean`
-
-Fail task if it encounters an error. Does not apply if you specify a `callback`.
-
-
-#### callback(err, stdout, stderr, cb)
-
-Default: `function () {}`  
-Type: `Function`
-
-Lets you override the default callback with your own.
-
-**Make sure to call the `cb` method when you're done.**
-
-
-#### execOptions
-
-Default: `undefined`  
-Accepts: Object
-
-Specify some options to be passed to the [.exec()](http://nodejs.org/api/child_process.html#child_process_child_process_exec_command_options_callback) method:
-
-- `cwd` String *Current working directory of the child process*
-- `env` Object *Environment key-value pairs*
-- `setsid` Boolean
-- `encoding` String *(Default: 'utf8')*
-- `timeout` Number *(Default: 0)*
-- `maxBuffer` Number *(Default: 200\*1024)*
-- `killSignal` String *(Default: 'SIGTERM')*
-
-
-## Upgrade from 0.1.4 to 0.2.0
-
-Because of the transition to grunt 0.4 there are some changes. To conform to new grunt standards, all options are now to be specified in an `options` object. I also took the opportunity to improve the task. The `stdout` and `stderr` options now only supports a boolean. If you want to do something with the result use the `callback` option. The `callback` option also changed.
-
-
-## Tests
-
-Grunt currently doesn't have a way to test tasks directly. You can test this task by running `grunt` and manually verify that it works.
-
-
-## License
-
-MIT License • © [Sindre Sorhus](http://sindresorhus.com)

data/vendor/node_modules/grunt-shell/tasks/shell.js

@@ -1,54 +0,0 @@
-'use strict';
-module.exports = function (grunt) {
-	var exec = require('child_process').exec;
-	var stripColors = require('stripcolorcodes');
-	var _ = grunt.util._;
-
-	grunt.registerMultiTask('shell', 'Run shell commands', function () {
-		var cb = this.async();
-		var options = this.options({
-			stdout: false,
-			stderr: false,
-			failOnError: false
-		});
-		var cmd = this.data.command;
-
-		if (cmd === undefined) {
-			throw new Error('`command` is required.');
-		}
-
-		cmd = grunt.template.process(_.isFunction(cmd) ? cmd.call(grunt) : cmd);
-
-		var cp = exec(cmd, options.execOptions, function (err, stdout, stderr) {
-			if (_.isFunction(options.callback)) {
-				options.callback.call(this, err, stdout, stderr, cb);
-			} else {
-				if (err && options.failOnError) {
-					grunt.warn(err);
-				}
-				cb();
-			}
-		});
-
-		var captureOutput = function (child, output) {
-			if (grunt.option('color') === false) {
-				child.on('data', function (data) {
-					output.write(stripColors(data));
-				});
-			} else {
-				child.pipe(output);
-			}
-		};
-
-		grunt.verbose.writeln('Command:', cmd.yellow);
-		grunt.verbose.writeflags(options, 'Options');
-
-		if (options.stdout || grunt.option('verbose')) {
-			captureOutput(cp.stdout, process.stdout);
-		}
-
-		if (options.stderr || grunt.option('verbose')) {
-			captureOutput(cp.stderr, process.stderr);
-		}
-	});
-};