Socket
Socket
Sign inDemoInstall

grunt-run

Package Overview
Dependencies
Maintainers
1
Versions
29
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

grunt-run - npm Package Compare versions

Comparing version 0.2.1 to 0.2.2

2

package.json
{
"name": "grunt-run",
"description": "Invite external commands into your grunt process with three tasks `run`, `wait` and `stop`.",
"version": "0.2.1",
"version": "0.2.2",
"homepage": "https://github.com/spenceralger/grunt-run",

@@ -6,0 +6,0 @@ "author": {

@@ -55,4 +55,13 @@ # grunt-run

Should this task wait until the script exits before finishing?
Should this task wait until the script exits before finishing? If you set this to false because you want to start a service of some sort before running another task, you can override this setting by passing the "keepalive" argument to the task call.
Example:
```sh
# start a testing instance of Elasticsearch and run some tests, `wait: false`
$ grunt run:es mocha:test
# override `wait` to keep Elasticsearch running
$ grunt run:es:keepalive
```
#### options.cwd

@@ -59,0 +68,0 @@ Type: `String`

@@ -38,3 +38,3 @@ /*

grunt.task.registerMultiTask('run', 'used to start external processes (like servers)', function () {
grunt.task.registerMultiTask('run', 'used to start external processes (like servers)', function (keepalive) {
var self = this;

@@ -54,2 +54,8 @@ var name = this.target;

});
if (keepalive === 'keepalive') {
// override the wait setting
opts.wait = true;
}
var spawnOpts = {

@@ -56,0 +62,0 @@ cwd: opts.cwd,

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc