zeekay / executive Goto Github PK

I have sth like this

exec.quiet( 'cat version.txt | jq -s -R -f version.jq' )

I am getting an error as result cat: invalid option -- 'R'
It seems that the output from cat isnt piping to the jq prog.

Whats wrong ?
Thanks for any support and best regards,
Nic

Version 0.5.19 of sake-cli just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As sake-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.6.5 of sake-bundle was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sake-bundle is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hey, suddenly this error appear in my app when I use node v.4.4.x

/home/rub/apps/test/node_modules/executive/dist/lib.js:226
var parse = function(args, opts = {}) {
                                ^

SyntaxError: Unexpected token =
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)

When running exec(['git reset --hard origin/master']); the origin/master gets converted to originmaster with the output then being: fatal: 'originmaster' does not appear to be a git repository

Hi, I was wondering if it is possible to pass in options from exec into executive, e.g. something like the maxBuffer listed here: https://nodejs.org/dist/latest-v8.x/docs/api/child_process.html#child_process_child_process_exec_command_options_callback

I added console.log(cmd, args) at https://github.com/zeekay/executive/blob/master/index.js#L148 to try and figure out why a command wasn't working correctly. It looks like multiple escaped spaces aren't being handled correctly:

exec.interactive('rsync --files-from="path\\\\ to\\\\ file"'); dumps out rsync [ '--files-from="path to\\ file"' ] - The second escaped space has \\.

Node child_process.spawn provides a way to forward process.env to sub processes, but Executive is not using them. See https://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options on the section describing the third argument.

However the following prints nothing:

const exec = require('executive')
process.env.NODE_ENV = 'test';
exec('echo $NODE_ENV').then(() => {
  console.log('done');
})

Say I have some untrusted text, is there a recommended way to escape the contents of the text as an argument?

  var exec = require('executive')
  var untrustedText = /* some text here */

  exec(`say '${untrustedText}'`)

In this example, I would assume that I have a shell injection vulnerability, since the untrustedText variable could have a single quote, i.e. hello'; rm -rf / which could hose my computer. Any idea how to fix this?

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

import exec from 'executive'
exec('uglifyjs foo.js --compress --mangle > foo.min.js')

when trying to compile it tsc will throw

src/force-dependency.ts:10:1 - error TS2693: 'exec' only refers to a type, but is being used as a value here.
10 exec('uglifyjs foo.js --compress --mangle > foo.min.js')

now don't have time for a PR just wanted to track this error here. thanks. Node 10.3, ts: 2.9.3

executive does not signal errors / throw exceptions if the command one tries to execute does not exist.

Simple repro:

const exec = require('executive');
const res = await exec(
      `hullu-bullu`,
      { strict: true }
    );
console.log(JSON.stringify(res));

Something emits this to my console:

Error: ENOENT, spawn hullu-bullu
Make sure 'hullu-bullu' exists and is executable.

However the console.log above produces:

{"status":0,"stderr":"","stdout":""}

Given that no exception is thrown (which is what I would expect as the command failed) and that status/stdout/stderr is empty, I have no way of catching the fact that the command did not succeed.

I have seen the issue on macOS 10.14 and ubuntu 16.04 with nodejs v10.15.3 LTS.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.1.6 of sake-test was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sake-test is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴