Would you take a quick second and ⭐️ my repo?
Helpers for Bash like shell scripting in JavaScript
jsh, pronounced "j shell", is a small JavaScript library (~20KB and no dependencies!) that provides helper aliases and functions that are similar to Bash syntax, allowing you to write shell scripts in JavaScript / Node.js that are simple and familiar.
Requirement: Node.js >=16
Create a file called script.js:
#!/usr/bin/env -S npx jsh
echo("Hello jsh!")
Make the file executable, run it, and you should see "Hello jsh" printed:
chmod +x ./script.js && ./script.js
> Hello jsh!
See detailed installation instructions below.
Below is a list of the available helpers. You can refer to the declaration file for a full list of the helpers and JSDoc documentation for arguments and usage.
All helpers listed below (except for the HTTP Requests helpers) are synchronous functions and will block while running.
General Scripting
| Description | |
|---|---|
echo("Hello") | Print text to console with trailing newline |
echo.yellow("Hello"),echo.green("Hello"),echo.red("Hello"),echo.blue("Hello") | Prints colored text to console with trailing newline |
printf("Processing...") | Print text to console without a trailing newline |
exit(1) | Halt the script and return an exit code |
error("An error", 1) | Echo an error and halt the script with an exit code |
const name = prompt("What is your name?"); | Prompt for user input and return after <Enter> pressed; also aliased as read(). |
sleep(2000) | Sleep for specified number of milliseconds (synchronous and will not block event loop) |
Command Execution (detailed docs below)
| Description | |
|---|---|
result=$("cmd.sh") | Execute a command and return the stdout |
exec("cmd.sh") | Execute a command and stream stdout to console without returning a value |
Arguments and Environment
| Description | |
|---|---|
$0 | Return the name of the entry script file (ex: my_script.js) |
$1, $2, $3 orargs[0], args[1], args[2] ... | Access arguments that have been passed |
args.source_file, args.v | Access arguments prefixed with "--" or "-". If argument is in format --source_file=input.txt the value of args.source_file would be "input.txt".If argument is in format --source_file or -v the argument name will be available on args as a true boolean (args.source_file == true, args.v == true) |
const [source_file, target_file] = args.assertCount(2) | Return arg values as array or call usage.printAndExit() if less than number of arguments specified were supplied. See details below. |
$HOME,env.HOME, or env["HOME"] | Access an environment variable |
const USER = env.assert("USER")orconst [HOME, USER] = env.assert(["HOME", "USER"]) | Return environment variable value or call usage.printAndExit() if undefined. You can also pass an array of environment variable names and an array of values will be returned. See details below. |
stdin() | Read stdin as a string |
usage("Usage: myscript.js [--verbose]") | Define a usage message. See details below. |
usage.printAndExit() | Print the usage message and then exit with an error exit code. If usage() was not previously called to define a usage message, a default one will be used. See details below. |
File System
| Description | |
|---|---|
cd("/usr/bin") | Change the current working directory |
config=readFile("cnf.txt") | Read text from file; also aliased as cat(). |
writeFile("cnf.txt", "World") | Write text to file |
readDir("./myDir") | Return absolute paths for files in a directory (recursive by default) |
dirExists("./myDir") | Check if directory exists |
mkDir("./newDirName") | Create a directory (recursive by default) |
rmDir("./newDirName") | Delete a directory (recursive by default) |
exists("./aFile.txt") | Check if a file exists |
rm("./myFile") | Delete a file |
dirName("./path/file.txt") | Return the directory name for a path |
__dirname | Returns the absolute path (directory) containing the entry script (works inside of CommonJS or ES module) |
__filename | Returns the name of the entry script (works inside of CommonJS or ES module) |
HTTP Requests (detailed docs below)
Note: The HTTP helper function are asynchronous and return a Promise.
| Description | |
|---|---|
await http.get("https://www.myapi.com") | Make a HTTP GET request and return the response body data |
await http.post("https://www.myapi.com", { data: "1" }, { Authorization: "Bearer abc123"}) | Make a HTTP POST request and return the response body data |
await http.put("https://www.myapi.com", { data: "1" }) | Make a HTTP PUT request and return the response body data |
await http.patch("https://www.myapi.com", { data: "1" }) | Make a HTTP PATCH request and return the response body data |
await http.delete("https://www.myapi.com", { data: "1" }) | Make a HTTP DELETE request and return the response body data |
await http("POST", "https://www.myapi.com", { data: "1" }, { headers: { Accept: "application/json" } }) | Make a HTTP request and return the response: ({ data, headers, statusCode, statusMessage }) |
await http.upload("https://www.myapi.com/logo", "./logo.jpg", "image/jpg") | Upload a file with a HTTP POST request |
await http.download("https://www.myapp.com/logo.jpg", "./logo.jpg") | Perform a HTTP GET request and save the response to a local file path |
#!/usr/bin/env npx jsh
usage(`\
Usage:
${$0} text target_file [--verbose]
Example:
${$0} "My text" ./test.txt --verbose
Writes some text to a file\
`);
const [text, target_file] = args.assertCount(2);
if (args.verbose) echo(`Writing text to file...`);
writeFile(target_file, text);
if (args.verbose) echo.green(`Done!`);
#!/usr/bin/env npx jsh
usage(`\
Usage:
${$0} prompt_text
Example:
${$0} "What is your name?"
Prompts for input and then echos it\
`);
const input = prompt($1); // `$1` contains the first argument which is prompt_text
echo(input);
When you want to run a command and buffer the output (stdout) of that command as a return value, you use the synchronous function $(). As the command is running, stdout will not be printed to the console but will instead be captured and returned as the result. This helper is intended for short running commands that do not produce a large amount of output.
Example:
// Will wait for `git status` to complete and assign output to `result` variable.
// Nothing will be printed to the console.
let result=$(`git status --porcelain`);
exec should be used when running commands where the output (stdout) does not need to be captured, but only printed to the console. This helper is intended for long running commands or those where output does not need to be captured.
Example:
// Will print `npm install` output immediately as it happens
// exec will not return anything (void)
exec(`npm install`)
> added 379 packages, and audited 380 packages in 1s
> 29 packages are looking for funding
> ...
If a command exits with a non-zero status, a CommandError error will be thrown. The error contains these properties: { message, command, stdout, stderr, status }.
Example:
try {
const output = $(`cat invalid.txt`)
} catch (err) {
echo(err.message) // Error running command: `cat invalid.txt`
echo(err.command) // cat invalid.txt
echo(err.stderr) // "cat: invalid.txt: No such file or directory"
echo(err.status) // 1
}
noThrow optionYou can pass in the option noThrow: true to prevent an error from being thrown. Instead, the stderr (or stdout) will be returned.
Example:
// This command will error out but will not throw because `$.noThrow()` was called.
let content=$(`cat invalid.txt`, { noThrow: true})
echo(content);
> cat: invalid.txt: No such file or directory
$() and exec() accept an options parameter object that may contain any of the following fields:
echoCommand: boolean - If true will echo the command itself before running it (Default: true for exec() and false for $())noThrow: boolean - If set to true, will not throw if the command returns a non-zero exit code (Default: false)timeout: number - In milliseconds the maximum amount of time the process is allowed to run (Default: undefined (unlimited))shell: string - By default, commands will be run inside of a shell (/bin/sh on *nix systems and process.env.ComSpec on Windows). This option can be used to specify the path to a different shell to execute commands with. For example, you could specify shell: "/bin/bash" to use bash.maxBuffer: number - Specifies the largest number of bytes allowed on stdout or stderr. If this value is exceeded, the child process will be terminated. (Default: 268435456 (256MB))To define usage instructions for your script, you can call usage() and pass in a usage string that describes the script and documents any required or optional arguments.
Example:
usage(`\
Usage:
json_formatter.js source_file target_file [--verbose]
Example:
json_formatter.js ./my_in_file.json ./my_out_file.json --verbose
Formats a JSON file
`);
You can also use $0 to reference the name of the current script rather than having to hardcode it. The above example could be changed to (${$0} source_file target_file [--verbose] ...).
You can call usage.printAndExit() at any time to print the usage instructions and then immediately exit with an error code. If you call usage.printAndExit() before calling usage(), a simple default message will be echoed but if you call usage.printAndExit() after calling usage(), your custom usage instructions will be echoed.
There are a few ways that usage.printAndExit() will be called implicitly:
--help or -h is passed in as an argument. (Note: in this case, the exit code will be set to 0)args.assertCount() is called and the required number of arguments were not passed in. For example, if args.assertCount(3) is called and only 2 arguments were passed in.env.assert() is called and the environment variable(s) are not defined.The http helper can be used to make asynchronous HTTP requests. It returns a promise and resolves with an IHttpResponse object that contains these properties: { data, headers, statusCode, statusMessage, requestOptions }.
Example:
const response = await http("GET", "https://www.myapi.com);
echo(response.data) // { message: "Testing" }
echo(response.headers) // { "Content-Type": "application/json" }
echo(response.statusCode) // 200
echo(response.statusMessage) // "OK"
There are also helpers for the primary HTTP methods: http.get, http.post, http.put, http.patch, and http.delete. These helpers do not require having to pass in the method type and will also return the response body data. If the response is of JSON format, it will be parsed before being returned.
Example:
const response = await http.get("https://www.myapi.com");
echo(response) // { message: "Testing" }
You can pass a data parameter which will then be sent as the body of the request. If you pass a JavaScript object, it will be converted to JSON and Content-Type, Accept, and Content-Length will be be automatically set, unless specified differently.
const newTask = { name: "My new task", completed: false };
await http.post("https://www.myapi.com/tasks", newTask, {
"Authorization": `Bearer ${env.API_AUTH_TOKEN}`
});
You may also pass a readable Stream as data. This is common when sending a file as part of a request.
const fs = require("fs");
const filePath = "./my_image.jpg";
const data = fs.createReadStream(filePath);
const fileSize = fs.statSync(filePath).size;
await http.post("https://fakeimageserver.com/uploads", data, {
"Content-Type": "image/jpeg",
"Content-Length": fileSize.toString(),
});
Note: If you are uploading a file, you can also use the http.upload() helper.
If any of the following headers are not specified, these default values will be used:
| Header | Value |
|---|---|
Accept | */* or application/json if data is an object |
Accept-Encoding | gzip |
Connection | close |
User-Agent | jsh |
If a status code outside the range 20X is returned in the HTTP response, a HttpRequestError error will be thrown. The error contains these properties: { message, data, statusCode, statusMessage, request, response }.
Example:
try {
const response = await http.post("https://www.myapi.com", { data: "1" });
} catch (err) {
echo(err.message) // "400 Bad Request"
echo(err.data) // { error: "The 'data' property is formatted incorrectly" }
echo(err.statusCode) // 400
echo(err.statusMessage) // Bad Request
}
noThrow optionYou can pass in the option noThrow: true when calling http() to prevent an error from being thrown when the response status is not 2xx. Instead, the response will be returned.
Example:
const response = await http("POST", "https://www.myapi.com", { data: 2 }, { noThrow: true });
echo(response.data) // "A server error occurred. Please try again later."
echo(response.headers) // { "Content-Type": "text/plain" }
echo(response.statusCode) // 500
echo(response.statusMessage) // "Internal Server Error"
http() accepts an options parameter object that may contain any of the following fields:
headers: object - The request headers to send with the request. A set of default headers will be included with the request even if not specified.timeout: number - The number of milliseconds of inactivity before a socket is presumed to have timed out (Default: 120000 (2 minutes))noFollowRedirects: boolean - Whether to not automatically follow 301 and 302 redirects. (Default: false)noThrow: boolean - If set to true, will not throw if the response status code is not 2xx (Default: false)omitResponseBodyInErrorMessage: boolean - If set to true, will not include the response body in a thrown error message (Default: false)Note: jsh requires Node >=16
By far the easiest way to use jsh is with a npx shebang.
Create a file called script.js:
#!/usr/bin/env -S npx jsh
echo("Hello jsh")
Note: The above shebang includes multiple arguments which will not work in some enviroments (including older versions of Linux). See this post for a workaround.
npx will look for a globally installed (npm install -g jsh) or locally installed (package.json / node_modules ) version of jsh, and use it if found. Otherwise, it will download the latest version from npm. Therefore, it is recommended to install jsh globally or locally when using npx so that it will be available and not have to be downloaded each time.
If you don't want to use npx, you can install jsh globally with npm:
npm install -g jsh
Once it is installed globally, you can write your script with a jsh shebang which will allow your script to be executed directly, with the globally installed jsh loaded at runtime. Run which jsh to locate the absolute path the jsh and use that for the shebang path.
#!/usr/bin/env jsh
echo(`Hello jsh`)
Rather than installing jsh globally, you can simply download it to a local folder and reference it directly from your script using a require or import statement. This is a good option for scripts running on a remote system where you may not have the ability to use npx or be able to install npm packages globally. Node.js will still need to be available, though.
First, download jsh:
curl -Lso jsh.cjs https://github.com/bradymholt/jsh/releases/latest/download/index.cjs
Then, in your script:
#!/usr/bin/env node
require('./jsh.cjs')
echo(`Hello jsh`)
When you write your shell scripts in jsh, you get to use a simple Bash like syntax but remember, it's still JavaScript! This means you can install npm packages and use them to your ❤️'s content.
Example:
npm install uuid
#!/usr/local/bin/jsh
require('uuid/v4')
echo(uuidv4()) // -> '110ec58a-a0f2-4ac4-8393-c866d813b8d1'
jsh is distributed as both a CommonJS and an ES Module library. When you require or import jsh, Node should be able to determine which library to load based upon your file extension (.js, .cjs, .mjs) and/or "type" setting in your package.json file.
TypeScript declarations for jsh are available and specified with "types": "index.d.ts" in the package.json file. A clean way to use TypeScript with jsh is by using ts-node.
Install ts-node, TypeScript, and jsh:
npm init -y && npm install ts-node typescript jsh
Create your jsh script file using a .ts file extension, following the below example.
myscript.ts
#!/usr/bin/env -S npx ts-node
import "jsh"
const contents: string = "Hello jsh from TypeScript";
echo(contents)
Note: The above shebang includes multiple arguments which will not work in some enviroments (including older versions of Linux). See this post for a workaround.
Run it: chmod +x ./myscript.ts && ./myscript.ts.
You can use jsh with TypeScript and ES Modules support so you can use features like top-level await.
Install ts-node, TypeScript, and jsh:
npm init -y && npm install ts-node typescript jsh
Ensure you have a package.json file defined with (at least) "type": "module" specified:
{
"type": "module"
}
Ensure you have a tsconfig.json file defined with (at least) the following config:
{
"compilerOptions": {
"target": "ESNext",
"module": "ESNext",
"moduleResolution": "node"
}
}
Create your jsh script, specifying ts-node-esm in the shebang:
myscript.ts
#!/usr/bin/env -S npx ts-node-esm
import "jsh"
echo("Hello jsh from TypeScript")
await new Promise((resolve) => setTimeout(resolve, 2000));
echo("Goodbye!")
Note: The above shebang includes multiple arguments which will not work in some enviroments (including older versions of Linux). See this post for a workaround.
Run it: chmod +x ./myscript.ts && ./myscript.ts
The following inline syntax can be used for jsh inside of a GitHub Actions workflow file.
jobs:
test:
runs-on: ubuntu-latest
steps:
- run: |
npm install jsh
node -r jsh <<EOF
echo("Hello");
setTimeout(()=> echo.yellow("Sleepyhead"), 5000);
EOF
jobs:
test:
runs-on: ubuntu-latest
steps:
- run: |
npm install ts-node jsh
node --loader ts-node/esm -r jsh --no-warnings --input-type=module <<EOF
echo("Hello");
await new Promise((resolve) => setTimeout(resolve, 5000));
echo.yellow("Sleepyhead");
EOF
FAQs
Helpers for Bash like shell scripting in JavaScript
The npm package jsh receives a total of 0 weekly downloads. As such, jsh popularity was classified as not popular.
We found that jsh demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.