1
0
Fork 0
toolkit/packages/exec
Jonathan Clem a2ab4bcf78
Publish
- @actions/core@1.1.0
 - @actions/exec@1.0.1
 - @actions/github@1.1.0
 - @actions/io@1.0.1
 - @actions/tool-cache@1.1.1
2019-09-05 11:03:19 -04:00
..
__tests__ Dont stamp over stdout (#29) 2019-07-11 15:02:45 -04:00
src Spelling (#72) 2019-08-21 15:31:44 -04:00
README.md fix syntax error in output example (#84) 2019-08-26 08:41:40 -04:00
RELEASES.md Add RELEASES.md for each package, bump tool-cache to publish (#67) 2019-08-22 13:14:49 -04:00
package-lock.json Update package versions to 1.0.0 (#42) 2019-08-07 12:56:34 -04:00
package.json Publish 2019-09-05 11:03:19 -04:00
tsconfig.json Add exec (#10) 2019-05-28 15:21:45 -04:00

README.md

@actions/exec

Usage

Basic

You can use this package to execute your tools on the command line in a cross platform way:

const exec = require('@actions/exec');

await exec.exec('node index.js');

Args

You can also pass in arg arrays:

const exec = require('@actions/exec');

await exec.exec('node', ['index.js', 'foo=bar']);

Output/options

Capture output or specify other options:

const exec = require('@actions/exec');

let myOutput = '';
let myError = '';

const options = {};
options.listeners = {
  stdout: (data: Buffer) => {
    myOutput += data.toString();
  },
  stderr: (data: Buffer) => {
    myError += data.toString();
  }
};
options.cwd = './lib';

await exec.exec('node', ['index.js', 'foo=bar'], options);

Exec tools not in the PATH

You can use it in conjunction with the which function from @actions/io to execute tools that are not in the PATH:

const exec = require('@actions/exec');
const io = require('@actions/io');

const pythonPath: string = await io.which('python', true)

await exec.exec(`"${pythonPath}"`, ['main.py']);