Git Product home page Git Product logo

shelljs's Introduction

ShellJS - Unix shell commands for Node.js

GitHub Actions Codecov npm version npm downloads

ShellJS is a portable (Windows/Linux/macOS) 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!

ShellJS is proudly tested on every node release since v8!

The project is unit-tested and battle-tested in projects like:

  • Firebug - Firefox's infamous debugger
  • JSHint & ESLint - popular JavaScript linters
  • Zepto - jQuery-compatible JavaScript library for modern browsers
  • Yeoman - Web application stack and development tool
  • Deployd.com - Open source PaaS for quick API backend generation
  • And many more.

If you have feedback, suggestions, or need help, feel free to post in our issue tracker.

Think ShellJS is cool? Check out some related projects in our Wiki page!

Upgrading from an older version? Check out our breaking changes page to see what changes to watch out for while upgrading.

Command line use

If you just want cross platform UNIX commands, checkout our new project shelljs/shx, a utility to expose shelljs to the command line.

For example:

$ shx mkdir -p foo
$ shx touch foo/bar.txt
$ shx rm -rf foo

Plugin API

ShellJS now supports third-party plugins! You can learn more about using plugins and writing your own ShellJS commands in the wiki.

A quick note about the docs

For documentation on all the latest features, check out our README. To read docs that are consistent with the latest release, check out the npm page.

Installing

Via npm:

$ npm install [-g] shelljs

Examples

var shell = require('shelljs');

if (!shell.which('git')) {
  shell.echo('Sorry, this script requires git');
  shell.exit(1);
}

// Copy files to release dir
shell.rm('-rf', 'out/Release');
shell.cp('-R', 'stuff/', 'out/Release');

// Replace macros in each .js file
shell.cd('lib');
shell.ls('*.js').forEach(function (file) {
  shell.sed('-i', 'BUILD_VERSION', 'v0.1.2', file);
  shell.sed('-i', /^.*REMOVE_THIS_LINE.*$/, '', file);
  shell.sed('-i', /.*REPLACE_LINE_WITH_MACRO.*\n/, shell.cat('macro.js'), file);
});
shell.cd('..');

// Run external tool synchronously
if (shell.exec('git commit -am "Auto-commit"').code !== 0) {
  shell.echo('Error: Git commit failed');
  shell.exit(1);
}

Exclude options

If you need to pass a parameter that looks like an option, you can do so like:

shell.grep('--', '-v', 'path/to/file'); // Search for "-v", no grep options

shell.cp('-R', '-dir', 'outdir'); // If already using an option, you're done

Global vs. Local

We no longer recommend using a global-import for ShellJS (i.e. require('shelljs/global')). While still supported for convenience, this pollutes the global namespace, and should therefore only be used with caution.

Instead, we recommend a local import (standard for npm packages):

var shell = require('shelljs');
shell.echo('hello world');

Alternatively, we also support importing as a module with:

import shell from 'shelljs';
shell.echo('hello world');

Command reference

All commands run synchronously, unless otherwise stated. All commands accept standard bash globbing characters (*, ?, etc.), compatible with the node glob module.

For less-commonly used commands and features, please check out our wiki page.

cat([options,] file [, file ...])

cat([options,] file_array)

Available options:

  • -n: number all output lines

Examples:

var str = cat('file*.txt');
var str = cat('file1', 'file2');
var str = cat(['file1', 'file2']); // same as above

Returns a ShellString containing the given file, or a concatenated string containing the files if more than one file is given (a new line character is introduced between each file).

cd([dir])

Changes to directory dir for the duration of the script. Changes to home directory if no argument is supplied. Returns a ShellString to indicate success or failure.

chmod([options,] octal_mode || octal_string, file)

chmod([options,] symbolic_mode, file)

Available options:

  • -v: output a diagnostic for every file processed
  • -c: like verbose, but report only when a change is made
  • -R: change files and directories recursively

Examples:

chmod(755, '/Users/brandon');
chmod('755', '/Users/brandon'); // same as above
chmod('u+x', '/Users/brandon');
chmod('-R', 'a-w', '/Users/brandon');

Alters the permissions of a file or directory by either specifying the absolute permissions in octal form or expressing the changes in symbols. This command tries to mimic the POSIX behavior as much as possible. Notable exceptions:

  • In symbolic modes, a-r and -r are identical. No consideration is given to the umask.
  • There is no "quiet" option, since default behavior is to run silent.
  • Windows OS uses a very different permission model than POSIX. chmod() does its best on Windows, but there are limits to how file permissions can be set. Note that WSL (Windows subsystem for Linux) does follow POSIX, so cross-platform compatibility should not be a concern there.

Returns a ShellString indicating success or failure.

cp([options,] source [, source ...], dest)

cp([options,] source_array, dest)

Available options:

  • -f: force (default behavior)
  • -n: no-clobber
  • -u: only copy if source is newer than dest
  • -r, -R: recursive
  • -L: follow symlinks
  • -P: don't follow symlinks
  • -p: preserve file mode, ownership, and timestamps

Examples:

cp('file1', 'dir1');
cp('-R', 'path/to/dir/', '~/newCopy/');
cp('-Rf', '/tmp/*', '/usr/local/*', '/home/tmp');
cp('-Rf', ['/tmp/*', '/usr/local/*'], '/home/tmp'); // same as above

Copies files. Returns a ShellString indicating success or failure.

pushd([options,] [dir | '-N' | '+N'])

Available options:

  • -n: Suppresses the normal change of directory when adding directories to the stack, so that only the stack is manipulated.
  • -q: Suppresses output to the console.

Arguments:

  • dir: Sets the current working directory to the top of the stack, then executes the equivalent of cd dir.
  • +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: 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.

Examples:

// process.cwd() === '/usr'
pushd('/etc'); // Returns /etc /usr
pushd('+1');   // Returns /usr /etc

Save the current directory on the top of the directory stack and then cd to dir. With no arguments, pushd exchanges the top two directories. Returns an array of paths in the stack.

popd([options,] ['-N' | '+N'])

Available options:

  • -n: Suppress the normal directory change when removing directories from the stack, so that only the stack is manipulated.
  • -q: Suppresses output to the console.

Arguments:

  • +N: Removes the Nth directory (counting from the left of the list printed by dirs), starting with zero.
  • -N: Removes the Nth directory (counting from the right of the list printed by dirs), starting with zero.

Examples:

echo(process.cwd()); // '/usr'
pushd('/etc');       // '/etc /usr'
echo(process.cwd()); // '/etc'
popd();              // '/usr'
echo(process.cwd()); // '/usr'

When 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.

dirs([options | '+N' | '-N'])

Available options:

  • -c: Clears the directory stack by deleting all of the elements.
  • -q: Suppresses output to the console.

Arguments:

  • +N: Displays the Nth directory (counting from the left of the list printed by dirs when invoked without options), starting with zero.
  • -N: Displays the Nth directory (counting from the right of the list printed by dirs when invoked without options), starting with zero.

Display the list of currently remembered directories. Returns an array of paths in the stack, or a single path if +N or -N was specified.

See also: pushd, popd

echo([options,] string [, string ...])

Available options:

  • -e: interpret backslash escapes (default)
  • -n: remove trailing newline from output

Examples:

echo('hello world');
var str = echo('hello world');
echo('-n', 'no newline at end');

Prints string to stdout, and returns a ShellString.

exec(command [, options] [, callback])

Available options:

  • async: Asynchronous execution. If a callback is provided, it will be set to true, regardless of the passed value (default: false).
  • fatal: Exit upon error (default: false).
  • silent: Do not echo program output to console (default: false).
  • encoding: Character encoding to use. Affects the values returned to stdout and stderr, and what is written to stdout and stderr when not in silent mode (default: 'utf8').
  • and any option available to Node.js's child_process.exec()

Examples:

var version = exec('node --version', {silent:true}).stdout;

var child = exec('some_long_running_process', {async:true});
child.stdout.on('data', function(data) {
  /* ... do something with data ... */
});

exec('some_long_running_process', function(code, stdout, stderr) {
  console.log('Exit code:', code);
  console.log('Program output:', stdout);
  console.log('Program stderr:', stderr);
});

Executes the given command synchronously, unless otherwise specified. When in synchronous mode, this returns a ShellString. Otherwise, this returns the child process object, and the callback receives the arguments (code, stdout, stderr).

Not seeing the behavior you want? exec() runs everything through sh by default (or cmd.exe on Windows), which differs from bash. If you need bash-specific behavior, try out the {shell: 'path/to/bash'} option.

Security note: as shell.exec() executes an arbitrary string in the system shell, it is critical to properly sanitize user input to avoid command injection. For more context, consult the Security Guidelines.

find(path [, path ...])

find(path_array)

Examples:

find('src', 'lib');
find(['src', 'lib']); // same as above
find('.').filter(function(file) { return file.match(/\.js$/); });

Returns a ShellString (with array-like properties) of all files (however deep) in the given paths.

The main difference from ls('-R', path) is that the resulting file names include the base directories (e.g., lib/resources/file1 instead of just file1).

grep([options,] regex_filter, file [, file ...])

grep([options,] regex_filter, file_array)

Available options:

  • -v: Invert regex_filter (only print non-matching lines).
  • -l: Print only filenames of matching files.
  • -i: Ignore case.
  • -n: Print line numbers.

Examples:

grep('-v', 'GLOBAL_VARIABLE', '*.js');
grep('GLOBAL_VARIABLE', '*.js');

Reads input string from given files and returns a ShellString containing all lines of the @ file that match the given regex_filter.

head([{'-n': <num>},] file [, file ...])

head([{'-n': <num>},] file_array)

Available options:

  • -n <num>: Show the first <num> lines of the files

Examples:

var str = head({'-n': 1}, 'file*.txt');
var str = head('file1', 'file2');
var str = head(['file1', 'file2']); // same as above

Read the start of a file. Returns a ShellString.

ln([options,] source, dest)

Available options:

  • -s: symlink
  • -f: force

Examples:

ln('file', 'newlink');
ln('-sf', 'file', 'existing');

Links source to dest. Use -f to force the link, should dest already exist. Returns a ShellString indicating success or failure.

ls([options,] [path, ...])

ls([options,] path_array)

Available options:

  • -R: recursive
  • -A: all files (include files beginning with ., except for . and ..)
  • -L: follow symlinks
  • -d: list directories themselves, not their contents
  • -l: provides more details for each file. Specifically, each file is represented by a structured object with separate fields for file metadata (see fs.Stats). The return value also overrides .toString() to resemble ls -l's output format for human readability, but programmatic usage should depend on the stable object format rather than the .toString() representation.

Examples:

ls('projs/*.js');
ls('projs/**/*.js'); // Find all js files recursively in projs
ls('-R', '/users/me', '/tmp');
ls('-R', ['/users/me', '/tmp']); // same as above
ls('-l', 'file.txt'); // { name: 'file.txt', mode: 33188, nlink: 1, ...}

Returns a ShellString (with array-like properties) of all the files in the given path, or files in the current directory if no path is provided.

mkdir([options,] dir [, dir ...])

mkdir([options,] dir_array)

Available options:

  • -p: full path (and create intermediate directories, if necessary)

Examples:

mkdir('-p', '/tmp/a/b/c/d', '/tmp/e/f/g');
mkdir('-p', ['/tmp/a/b/c/d', '/tmp/e/f/g']); // same as above

Creates directories. Returns a ShellString indicating success or failure.

mv([options ,] source [, source ...], dest')

mv([options ,] source_array, dest')

Available options:

  • -f: force (default behavior)
  • -n: no-clobber

Examples:

mv('-n', 'file', 'dir/');
mv('file1', 'file2', 'dir/');
mv(['file1', 'file2'], 'dir/'); // same as above

Moves source file(s) to dest. Returns a ShellString indicating success or failure.

pwd()

Returns the current directory as a ShellString.

rm([options,] file [, file ...])

rm([options,] file_array)

Available options:

  • -f: force
  • -r, -R: recursive

Examples:

rm('-rf', '/tmp/*');
rm('some_file.txt', 'another_file.txt');
rm(['some_file.txt', 'another_file.txt']); // same as above

Removes files. Returns a ShellString indicating success or failure.

sed([options,] search_regex, replacement, file [, file ...])

sed([options,] search_regex, replacement, file_array)

Available options:

  • -i: Replace contents of file in-place. Note that no backups will be created!

Examples:

sed('-i', 'PROGRAM_VERSION', 'v0.1.3', 'source.js');

Reads an input string from files, line by line, and performs a JavaScript replace() on each of the lines from the input string using the given search_regex and replacement string or function. Returns the new ShellString after replacement.

Note:

Like unix sed, ShellJS sed supports capture groups. Capture groups are specified using the $n syntax:

sed(/(\w+)\s(\w+)/, '$2, $1', 'file.txt');

Also, like unix sed, ShellJS sed runs replacements on each line from the input file (split by '\n') separately, so search_regexes that span more than one line (or include '\n') will not match anything and nothing will be replaced.

set(options)

Available options:

  • +/-e: exit upon error (config.fatal)
  • +/-v: verbose: show all commands (config.verbose)
  • +/-f: disable filename expansion (globbing)

Examples:

set('-e'); // exit upon first error
set('+e'); // this undoes a "set('-e')"

Sets global configuration variables.

sort([options,] file [, file ...])

sort([options,] file_array)

Available options:

  • -r: Reverse the results
  • -n: Compare according to numerical value

Examples:

sort('foo.txt', 'bar.txt');
sort('-r', 'foo.txt');

Return the contents of the files, sorted line-by-line as a ShellString. Sorting multiple files mixes their content (just as unix sort does).

tail([{'-n': <num>},] file [, file ...])

tail([{'-n': <num>},] file_array)

Available options:

  • -n <num>: Show the last <num> lines of files

Examples:

var str = tail({'-n': 1}, 'file*.txt');
var str = tail('file1', 'file2');
var str = tail(['file1', 'file2']); // same as above

Read the end of a file. Returns a ShellString.

tempdir()

Examples:

var tmp = tempdir(); // "/tmp" for most *nix platforms

Searches and returns string containing a writeable, platform-dependent temporary directory. Follows Python's tempfile algorithm.

test(expression)

Available expression primaries:

  • '-b', 'path': true if path is a block device
  • '-c', 'path': true if path is a character device
  • '-d', 'path': true if path is a directory
  • '-e', 'path': true if path exists
  • '-f', 'path': true if path is a regular file
  • '-L', 'path': true if path is a symbolic link
  • '-p', 'path': true if path is a pipe (FIFO)
  • '-S', 'path': true if path is a socket

Examples:

if (test('-d', path)) { /* do something with dir */ };
if (!test('-f', path)) continue; // skip if it's not a regular file

Evaluates expression using the available primaries and returns corresponding boolean value.

ShellString.prototype.to(file)

Examples:

cat('input.txt').to('output.txt');

Analogous to the redirection operator > in Unix, but works with ShellStrings (such as those returned by cat, grep, etc.). Like Unix redirections, to() will overwrite any existing file! Returns the same ShellString this operated on, to support chaining.

ShellString.prototype.toEnd(file)

Examples:

cat('input.txt').toEnd('output.txt');

Analogous to the redirect-and-append operator >> in Unix, but works with ShellStrings (such as those returned by cat, grep, etc.). Returns the same ShellString this operated on, to support chaining.

touch([options,] file [, file ...])

touch([options,] file_array)

Available options:

  • -a: Change only the access time
  • -c: Do not create any files
  • -m: Change only the modification time
  • {'-d': someDate}, {date: someDate}: Use a Date instance (ex. someDate) instead of current time
  • {'-r': file}, {reference: file}: Use file's times instead of current time

Examples:

touch('source.js');
touch('-c', 'path/to/file.js');
touch({ '-r': 'referenceFile.txt' }, 'path/to/file.js');
touch({ '-d': new Date('December 17, 1995 03:24:00'), '-m': true }, 'path/to/file.js');
touch({ date: new Date('December 17, 1995 03:24:00') }, 'path/to/file.js');

Update the access and modification times of each file to the current time. A file argument that does not exist is created empty, unless -c is supplied. This is a partial implementation of touch(1). Returns a ShellString indicating success or failure.

uniq([options,] [input, [output]])

Available options:

  • -i: Ignore case while comparing
  • -c: Prefix lines by the number of occurrences
  • -d: Only print duplicate lines, one for each group of identical lines

Examples:

uniq('foo.txt');
uniq('-i', 'foo.txt');
uniq('-cd', 'foo.txt', 'bar.txt');

Filter adjacent matching lines from input. Returns a ShellString.

which(command)

Examples:

var nodeExec = which('node');

Searches for command in the system's PATH. On Windows, this uses the PATHEXT variable to append the extension if it's not already executable. Returns a ShellString containing the absolute path to command.

exit(code)

Exits the current process with the given exit code.

error()

Tests if error occurred in the last command. Returns a truthy value if an error returned, or a falsy value otherwise.

Note: do not rely on the return value to be an error message. If you need the last error message, use the .stderr attribute from the last command's return value instead.

errorCode()

Returns the error code from the last command.

ShellString(str)

Examples:

var foo = new ShellString('hello world');

This is a dedicated type returned by most ShellJS methods, which wraps a string (or array) value. This has all the string (or array) methods, but also exposes extra methods: .to(), .toEnd(), and all the pipe-able methods (ex. .cat(), .grep(), etc.). This can be easily converted into a string by calling .toString().

This type also exposes the corresponding command's stdout, stderr, and return status code via the .stdout (string), .stderr (string), and .code (number) properties respectively.

env['VAR_NAME']

Object containing environment variables (both getter and setter). Shortcut to process.env.

Pipes

Examples:

grep('foo', 'file1.txt', 'file2.txt').sed(/o/g, 'a').to('output.txt');
echo('files with o\'s in the name:\n' + ls().grep('o'));
cat('test.js').exec('node'); // pipe to exec() call

Commands can send their output to another command in a pipe-like fashion. sed, grep, cat, exec, to, and toEnd can appear on the right-hand side of a pipe. Pipes can be chained.

Configuration

config.silent

Example:

var sh = require('shelljs');
var silentState = sh.config.silent; // save old silent state
sh.config.silent = true;
/* ... */
sh.config.silent = silentState; // restore old silent state

Suppresses all command output if true, except for echo() calls. Default is false.

config.fatal

Example:

require('shelljs/global');
config.fatal = true; // or set('-e');
cp('this_file_does_not_exist', '/dev/null'); // throws Error here
/* more commands... */

If true, the script will throw a Javascript error when any shell.js command encounters an error. Default is false. This is analogous to Bash's set -e.

config.verbose

Example:

config.verbose = true; // or set('-v');
cd('dir/');
rm('-rf', 'foo.txt', 'bar.txt');
exec('echo hello');

Will print each command as follows:

cd dir/
rm -rf foo.txt bar.txt
exec echo hello

config.globOptions

Example:

config.globOptions = {nodir: true};

Use this value for calls to glob.sync() instead of the default options.

config.reset()

Example:

var shell = require('shelljs');
// Make changes to shell.config, and do stuff...
/* ... */
shell.config.reset(); // reset to original state
// Do more stuff, but with original settings
/* ... */

Reset shell.config to the defaults:

{
  fatal: false,
  globOptions: {},
  maxdepth: 255,
  noglob: false,
  silent: false,
  verbose: false,
}

Team

Nate Fischer Brandon Freitag
Nate Fischer Brandon Freitag

shelljs's People

Contributors

a10y avatar aeosynth avatar ando-takahiro avatar andreialecu avatar ariporad avatar arturadib avatar brandonramirez avatar byk avatar danielepolencic avatar deining avatar frandiox avatar freitagbr avatar gyandeeps avatar iapain avatar idearat avatar jamon avatar jessiefrance avatar joshi-sh avatar julianlaval avatar keskival avatar madrobby avatar mstade avatar nfischer avatar rezonant avatar schoonology avatar termosa avatar timothygu avatar tingluohuang avatar utensil avatar wyardley avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

shelljs's Issues

Not declared local var implies possible memory leak

While executing testing with Mocha over a Restify server using shelljs module, appears a "possible" memory leak due tu a variable declared as global since it is not declared locally.

Script with the problem: shell.js
Line: 994
"Problematic" code: "for (letter in map)"

Var letter is not declared locally.

how to read console input

following code snipper works using 'node' command, but not works using 'sjs' command

process.stdin.on('data', function (chunk) {
  process.stdout.write('data: ' + chunk);
}).resume();

cp skipping dot files?

It appears cp is skipping dot files.

var sh = require('shelljs')
sh.cp('-R', 'foo/*', 'bar')

where foo contains an .htaccess file among whatever else, bar fails to receive the file.

Tested on Windows 7, NodeJS v0.10.17

Executing SSH with ShellJs

Hi all,
is it possible to execute an ssh command with shelljs? I get the following error
Pseudo-terminal will not be allocated because stdin is not a terminal.

If it is possible to execute ssh command with shelljs, could someone point me to a link or example.
Thanks
José

shelljs.exec stalls on Red Hat when script is invoked with 'sudo -u username'

This is something that happens only on Red Hat as far as I know.
I'm running a npm module as a different user thant the one currently logged in, for example:
sudo -u username client.js

This works normally on Ubuntu and Debian, but on Red Hat it gets stuck indefinitely on this line:
response = shell.exec('whoami', { silent: true });

(it doesn't work for any command, not just whoami)

Everything works okay when the script is kicked off normaly (without sudo).

spawn EMFILE

Hi,
i want to import 20000 Document files in node.js.

after 300 exec calls I get:

shell.js: internal error
Error: spawn EMFILE
at errnoException (child_process.js:980:11)
at ChildProcess.spawn (child_process.js:927:11)
at exports.spawn (child_process.js:715:9)
at Object.exports.execFile (child_process.js:607:15)
at Object.exports.exec (child_process.js:578:18)
at execSync (/var/www/filesearch/node_modules/shelljs/shell.js:1793:9)
at _exec (/var/www/filesearch/node_modules/shelljs/shell.js:1130:12)
at /var/www/filesearch/node_modules/shelljs/shell.js:1487:23
at FileScanner.ingestDB (/var/www/filesearch/crawl/filescanner.js:41:25)
at callbacks (/var/www/filesearch/node_modules/express/lib/router/index.js:161:37)

I tried it asynchon or synchron. It seems fpr me that the file handle in exec is not closed.

ulimit -n xxx doesn't help here ..

You can reproduce this behaviour with following snippet:

    for(i=0;i<1000;i++) {
        var child = exec('node -v', {async:false});
        console.log(i);
    }

TIA
Michael

Using shelljs in a CLI app.

Hello. When I run shelljs in a CLI app I get the following message (even if I just include it):

to: wrong arguments

toEnd: wrong arguments.

So this is when it is inside a file that I just run something like ./bin/sh.

!/usr/bin/env node

Any thoughts on why this would be?

This is probably something really silly. But can someone take a look? This is the repo:

https://github.com/Jonovono/une

And you can see the occurance happening when I include shelljs in: https://github.com/Jonovono/UNE/blob/master/lib/files.js

Even if I have shell.mv commented out it still happens. If I include shelljs somewhere else it is fine.

Cross-platform way to add to PATH

I'm sure part of this should be fixed in node core, but they're just sitting on the issue (nodejs/node-v0.x-archive#3728).

PATH uses : on *nix, and ; on Windows. It could either provide just the separator, or provide some sort of push method.

Example:

shell.PATH.push('../node_modules/.bin');
// or
shell.env.PATH += shell.sep + '../node_modules/.bin';

We need sed -n ?

Some like sed('-n','/FOO/,/BAR/p',cat("cats.txt"));
says sed: option not recognized: n

global.key assigned value 'async' as a result of shell.exec(...)

I recently integrated shelljs into one of my projects and mocha started complaining about a global leak with respect to a key property being set on the global object.

I can reproduce the effect in the REPL, i.e. independently of the project in question:

$ node
> var shell = require('shelljs');
undefined
> global.key
undefined
> shell.exec('ls -lad *');
{ code: 0,
  output: ... }
> global.key
'async'

If this is an expected behavior, it might be good to document it in shelljs's README, as it took me a little while to figure out that I hadn't caused the "leak" with a statement in my own code. I imagine it may trip up other folks as well.

Is it a bug perhaps?

By the way, many thanks for creating shelljs. I ran into a situation recently where I just had to have a way to make a synchronous http request. Using shelljs to synchronously invoke another node script which makes the request asynchronously ended up being a far simpler solution than introducing fibers or hand-rolling a C addon.

Rewrite exec using execsync-ng (which uses node-ffi)

Hi,

Shelljs has been awesome so far, except for exec. I know how it works, with the write-to-a-temporary file loop, and I know that its a hack necessary due to the lack of child_process.execSync.

Unfortunately, exec has been very buggy for me, randomly not working on various developer and server machines. Usually it gets stuck in an endless loop. I never seem to be able to satisfyingly reproduce the issue or find the cause.

So I decided to give that up and write shelljs-ffi based on execsync-ng which in turn is based on node-ffi. execsync-ng is a fork of execSync that also works on windows.

You can check out these modules at https://github.com/doxout/shelljs and https://github.com/doxout/execSync or try them out: npm install shelljs-ffi execsync-ng

I know that a native module dependency such as node-ffi is probably unacceptable for shelljs. However I decided to ask anyway... Is it possible that this fork may be accepted into shelljs?

`mv` fails on block, character, fifo

from #23:

a block device (mknod test/resources/block b 1 1) causes the following error:

Running test: mv.js
shell.js: internal error
Error: UNKNOWN, unknown error
    at Object.fs.readSync (fs.js:381:19)
    at copyFileSync (/Users/james/src/assets/shelljs/shell.js:1119:20)
    at /Users/james/src/assets/shelljs/shell.js:311:5
    at Array.forEach (native)
    at Object._cp (/Users/james/src/assets/shelljs/shell.js:270:11)
    at Object.cp (/Users/james/src/assets/shelljs/shell.js:1074:23)
    at Object.<anonymous> (/Users/james/src/assets/shelljs/test/mv.js:20:7)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)

a character device (mknod test/resources/character c 1 1) and fifo (mkfifo test/resources/fifo) causes the mv test to hang

symlink, file, directory work fine. haven't tested sockets.

shelljs cp handling symlinks badly

Making a build script for a project. using shelljs/make in coffeescript.
when I try to call this function:
cp '-fR', build_dir+'/*', dest_dir

node kicks back this ugly chunk:

shell.js: internal error
Error: EEXIST, file already exists '/[dest_dir]/node_modules/.bin/express'
  at Object.fs.symlinkSync (fs.js:730:18)
  at cpdirSyncRecursive (/[redac]/node_modules/shelljs/shell.js:1575:10)
  at cpdirSyncRecursive (/redac]/node_modules/shelljs/shell.js:1572:7)
  at /redac]/node_modules/shelljs/shell.js:325:9
  at Array.forEach (native)
  at _cp (/redac]/node_modules/shelljs/shell.js:302:11)
  at /redac]/node_modules/shelljs/shell.js:1491:23
  at Function.target.install (/redac]/grind:65:3, <js>:63:5)
  at Object.target.(anonymous function) [as install] (/redac]/node_modules/shelljs/make.js:28:26)
  at Function.target.fast (/redac]/grind:25:3, <js>:19:12)
  at Object.target.(anonymous function) [as fast] (/redac]/node_modules/shelljs/make.js:28:26)
  at /redac]/node_modules/shelljs/make.js:38:20
  at Array.forEach (native)
  at [object Object]._onTimeout (/redac]/node_modules/shelljs/make.js:36:10)
  at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

The symlink in question from the source directory is:
../express/bin/express
Also, I'm overwriting whatever is in the destination in this instance. That file and the express file exists, I'm sure.

On the other hand, exec "cp -rf #{build_dir}/* #{dest_dir}" works perfectly as intended.

I'll take a crack at looking at the source later and seeing what it might be, just wanted to log it while I'm still thinking about it.

Synchronous exec stalls permenantly when there is an error/w the shell

This ShellJS script will stall indefinitely, if 'nosuchfile.txt' doesn't exist.

require('shelljs/global')

exec("cat < nosuchfile.txt")

Will cause shelljs to stall

This fixes it:

  cmd += ' > '+stdoutFile+' 2>&1'; // works on both win/unix

  var script =
   "var child = require('child_process'), path=require('path'), \
        fs = require('fs'); \
    child.exec('"+escape(cmd)+"', {env: process.env}, function(err,stdout,stderr) { \
      fs.writeFileSync('"+escape(codeFile)+"', err ? err.code.toString() : '0'); \
      if(!path.existsSync('"+escape(stdoutFile)+"')){ fs.writeFileSync('"+escape(stdoutFile)+"',stdout.toString()+stderr.toString()); }; \
    }); \
    process.on('uncaughtException',function(err){ \
      if(!path.existsSync('"+escape(stdoutFile)+"')){ fs.writeFileSync('"+escape(stdoutFile)+"',err.toString()); } \
      if(!path.existsSync('"+escape(codeFile)+"')){ fs.writeFileSync('"+escape(codeFile)+"','-1'); } \
    }); \
    process.on('exit',function(){ \
      if(!path.existsSync('"+escape(stdoutFile)+"')){ fs.writeFileSync('"+escape(stdoutFile)+"','Uncaught ShellJS Error'); } \
      if(!path.existsSync('"+escape(codeFile)+"')){ fs.writeFileSync('"+escape(codeFile)+"','-1'); } \
    });"


  if (fs.existsSync(scriptFile)) _unlinkSync(scriptFile);
  if (fs.existsSync(stdoutFile)) _unlinkSync(stdoutFile);
  if (fs.existsSync(codeFile)) _unlinkSync(codeFile);

We have forked your repo, here: https://github.com/croteb/shelljs and will be keeping it current with our fixes.

Thanks!

silent output

Would be nice if there was a way to silent the ouput, for use in systems like grunt that have their own output. For example:

var hash = shell.exec('git rev-parse --short HEAD').output;

Now I have access to the git hash (yay), but that hash has been displayed in the console (boo).

Handling permissions errors on file I/O

It would be nice if shelljs gracefully handled file I/O errors due to permissions issues, as opposed to the current full error dump you get now:

    var shelljs = require('./shelljs');
    shelljs.mkdir('-p', '/var/log/myNewDir');

    $ node shelljsConsumer.js
    shell.js: internal error
    Error: EACCES, permission denied '/var/log/myNewDir'
        at Object.fs.mkdirSync (fs.js:642:18)
        at mkdirSyncRecursive (shell.js:1649:8)
        at shell.js:541:7
        at Array.forEach (native)
        at Object._mkdir (shell.js:526:8)
        at Object.mkdir (shell.js:1491:23)
        at Object.<anonymous> (shelljsConsumer.js:2:10)
        at Module._compile (module.js:456:26)
        at Object.Module._extensions..js (module.js:474:10)
        at Module.load (module.js:356:32)

It seems like, for a lot of use cases (like this one), a more user-friendly error handling path could be initiated.

Redirect output to file fails

When executing the following command directly on the cmd line the database is dumped to the file correctly.

When running the same command via .exec. using Grunt.js (see below) the output is in the console and the file is created but has no contents.

shell.exec('mysqldump -u my_user -pmy_pass test > test.sql');

My ultimate goal is to run a dump via ssh like so:

shell.exec("ssh user@host \ mysqldump -u my_user -pmy_pass test > test.sql");

Exporting variables.

I was wondering what is the best way to do something like

export PATH=/usr/bin:$PATH

with shelljs. I guess you can use env, but I tried to change PS1 on linux and nothing happens.
I am particulary interested in changing PS1 somehow from within node.

"For convenient iteration via `for in`, ..."?

ls and find return objects (e.g. { 'file1':null, 'dir1/file2':null, ...}), supposedly for convenience. Sure, it's nice when you're doing a for in, but I'm not sure why you would. This is V8 we're talking about, why not use arrays since we have access to the full set of ES5 iteration and accessor methods? (e.g. forEach, filter, map, reduce, indexOf)

I'd be happy to submit a pull request if there is a desire for one :)

Error ENOTEMPTY when deleting a directory recursively.

Sometimes, when deleting a directory that has sub-directories and files it throw an error witch code: ENOTEMPTY.

When executing this: rm('-rf', '/path/to/build/zip') the following error is thrown:

rm: could not remove directory (code ENOTEMPTY): build/zip/vendors/bootstrap

Note: It can happen with any sub-directory, is not related to a particular directory only. It doesn't happens with files.

exec with callback should automatically be async

I see that the code allows for you to do exec(cmd, callback), and it will create an empty options object. However, this will mean async is false, so the callback is not used.

It seems like if you passed a callback, you expect it to be async?

pushd/popd

shouldn't be hard to implement, would be awesome if someone implemented it :)

Inconsistent behaviour of cp command with directories.

cp command behaves differently from their shell parent.
Suppose, we have the following structure:

  • dir1/
    • lib/
      • main.js

Or in shelljs code:

require('shelljs/global')
mkdir('dir1')
mkdir('dir1/lib')
echo('123').to('dir1/lib/main.js');

All these commands fail on my system:

cp('-r', 'dir1/*', 'dir2/')
shell.js: internal error
Error: ENOENT, no such file or directory 'dir2//lib'
at Object.fs.mkdirSync (fs.js:483:18)
at code/node_modules/shelljs/shell.js:306:14
at Array.forEach (native)
at _cp (code/node_modules/shelljs/shell.js:288:11)
at code/node_modules/shelljs/shell.js:1103:23
at repl:1:2
at REPLServer.self.eval (repl.js:111:21)
at Interface. (repl.js:250:12)
at Interface.EventEmitter.emit (events.js:93:17)
at Interface._onLine (readline.js:199:10)

cp('-r', 'dir1', 'dir2');
shell.js: internal error
Error: ENOENT, no such file or directory 'dir2/dir1'
at Object.fs.mkdirSync (fs.js:483:18)
at code/node_modules/shelljs/shell.js:306:14
at Array.forEach (native)
at _cp (code/node_modules/shelljs/shell.js:288:11)
at code/node_modules/shelljs/shell.js:1103:23
at repl:1:1
at REPLServer.self.eval (repl.js:111:21)
at rli.on.self.bufferedCmd (repl.js:260:20)
at REPLServer.self.eval (repl.js:118:5)
at Interface. (repl.js:250:12)

cp('-r', 'dir1/', 'dir2/')
shell.js: internal error
Error: ENOENT, no such file or directory 'dir2//lib'
at Object.fs.mkdirSync (fs.js:483:18)
at code/node_modules/shelljs/shell.js:306:14
at Array.forEach (native)
at _cp (code/node_modules/shelljs/shell.js:288:11)
at code/node_modules/shelljs/shell.js:1103:23
at repl:1:2
at REPLServer.self.eval (repl.js:111:21)
at Interface. (repl.js:250:12)
at Interface.EventEmitter.emit (events.js:93:17)
at Interface._onLine (readline.js:199:10)

cp('-R', 'dir1/', 'dir2');
shell.js: internal error
Error: ENOENT, no such file or directory 'dir2/lib'
at Object.fs.mkdirSync (fs.js:483:18)
at code/node_modules/shelljs/shell.js:306:14
at Array.forEach (native)
at _cp (code/node_modules/shelljs/shell.js:288:11)
at code/node_modules/shelljs/shell.js:1103:23
at repl:1:1
at REPLServer.self.eval (repl.js:111:21)
at rli.on.self.bufferedCmd (repl.js:260:20)
at REPLServer.self.eval (repl.js:118:5)
at Interface. (repl.js:250:12)

but all this calls successfully run if I've created the dir2 directory previously.

cp from bash always creates target directory (only one level) if necessary. So all these calls finish successfully.

interpret `--` as stdin

in jshint/jshint#687, there's an interest in being able to use the jshint cli interface by passing -- as a filename and having the input from stdin used as the contents of the file. since jshint uses shelljs i was wondering if it would be possible to add this support to shelljs - it's probably useful to lots of other people who use shelljs too.

i'm not very familiar with shelljs but if someone could give me some guidance on how to approach this, i might take a stab at it.

Versions 0.2.4 and 0.2.3 keep throwing strange errors

I have a nodejs script that runs a lot of shell commands. In the last few days, script strarted throwing strange errors, but it continued to work.
This was the error on CentOS:
exec: Exec returned error code1

and this on Ubuntu:
exec: Exec returned error code127

When I changed the script dependencies to sue shelljs v0.2.2 the errors stopped appearing.
Note that the errors were only shown when the script was installed with npm, when it was called directly from the local repository there were no errors.

rm() does not respect read/write modes

Moreover things seem to behave differently on Windows vs. Unix.

This seems to be partly because of different behaviors of fs.unlink, partly because of our implementation.

stat

I'd like to be able to do things like

compile "source" if not mtime "source" < mtime "out"

so either mtime, atime, ctime functions or else support the "-ot" and "-nt" tests or else a stat function that basically wraps fs.stat.

Or all of the above 😁

debug flag that prints commands instead of executing

Make has a debug flag:

-n, --just-print, --dry-run, --recon
  Print the commands that would be executed, but do not execute them.

It would be great to have this flag present to help debug a non-functional shelljs script. Maybe just have it print the command to the console rather than execute the command? or do both?

Detecting shelljs/node

Is there a way detect if shelljs or node is installed in the system, within the script. I know it's kina dumb but, say in bash script it's possible to get the the $SHELL

Asking this because, say one decides to write a setup script with shelljs, then node becomes a dependency to get shelljs first....so bit confused... env['NODE_PATH'] would be useful? But also, can we know if shelljs is installed or not and then install it within shelljs 0_o

100% cpu usage when a nodejs script goes side ways executing a command.

Hi,

First thanks for writing ShellJS, so we've noticed in our project that somtimes shellJS consumes 100% cpu resources when something goes wrong with exec.

i.e.

exec("mysql -u testUser testDB < test.sql")

will sometimes hang, leaving us with 100% cpu utilization on the shellJS parent process.

Unexpected cp behaviour with directories

With unix cp you can do

cp -Rf oneDir/ twoDir/

which copies all the files in oneDir into twoDir. When I do:

cp('-Rf', 'oneDir/', '/twoDir/');

nothing gets copied, I have to do

cp('-Rf', 'oneDir/*', '/twoDir/');

from man cp

If source_file designates a directory, cp copies the directory and the entire subtree connected
at that point. If the source_file ends in a /, the contents of the directory are copied rather
than the directory itself.

#mv Won't Work Across Disks

fs#renameSync won't work across partitions or attached storage. This is by design, as rename is paired to the C version of the same method, which isn't able to cross disks either. (See this closed issue for more discussion about rename.)

A solution could be piping a readStream to a writeStream, and then cleaning up the source file.
I'd attach a fix but the trouble is that listening for the end event on the pipe and firing a callback would break the synchronous nature of shelljs.

Ideas?

Great module, by the way. Very helpful!

asynchronous exec

Hi,
I am trying to use the exec function in an asynchronous code as follows


shell = require 'shelljs'
shell.exec('ssh -l username host \"cd Desktop; touch example.txt\"', (code, output) ->
console.log code
)

Although the command is executed successfully, it doesn't print the code. So I have no way in my code to know what happened to the ssh command. Is there a different way of calling exec asynchronously?
Note that the synchronous case works perfectly
Thanks
José

`exec` gets stuck on my Debian box

protzenk@sauternes:pdfjs ((a68e11c...)) $ nodejs
> require("shelljs/global")
{}
> exec("ls")

Then, the nodejs process gets stuck and the only way I can get out of this is to run pkill nodejs in another terminal. Any ideas what might be causing this? I've installed nodejs as a Debian package, and I've also run "npm install shelljs" hoping that it would upgrade me to the latest version.

Thanks,

jonathan

ls -l

I'd like to at least see the file type (file, directory, symlink, etc) and size.

Some packages that may be helpful

What about other commands?

What about other commands? Suppose I want to do cat "file.txt" | less, how do I do that? Or what about pacman -S awesome-package (Arch's package manager)?

From the looks of it, I don't think I can, can I?

$variables in exec() aren't handled correctly

An example shell script I'm using: lsof -i :80 | grep node | awk '{ printf $2 }'

What this should print out is the PID of the node process running on port 80; instead it returns awk: line 1: no arguments in call to printf. I can recreate this error by deleting the $2 and running it on my terminal. I suspect that shelljs or node is incorrectly escaping or interpolating the $2 variable; I haven't figured out the magical number of slashes to escape it properly.

which and node_modules

i know it's not (at all) mimicking which(1), but imo, it'd be cool if shelljs.which() would check for binaries in module.paths.

thoughts?

i'd be happy to add this behavior if you like the idea.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.