`process.exitCode` behavior back-ported from io.js and Node.js 0.12+
Run binaries from node, with easy stdout/stderr manipulation + signal passthrough + exit code propagation.
Execute a callback when the process exits, passing the exit code (ESM/CJS)
Terminate Node-RED by setting exit code.
Cross-platform CLI wrapper that runs any command and exits with zero
Node.js program finisher - run your last callback with `exit code` and `signal name` as arguments
Scan a user's NPM tokens and fail with exit code 1 if any exceed a maximum age in days.
Sets the exit code appropriately, given some tap output.
Receives streaming TAP, passes it through, and sets the process exit code to 1 if there are any failing tests.
Duplexes stdout and stderr to a file, like tee, but also forwards the exit code of the original process
Fail with an error message and a correct exit code
run commands in parallel, exit all when one ends. exit code used to exit main process. ``` -x to run noisily (pipe to stdout/stderr) -s to run silently (dont pipe to stdout/stderr) ```
Shell-wrapper hook binaries — agent-agnostic command gating via shell-AST. Decisions surface through stdout/stderr/exit-code; works for any caller (agent, human, CI).
Run generated binaries having last exit code in a map
Detect whether a command fails, and invert exit code.
Deterministic, zero-token CLI for Pipeline. Mirrors the hosted MCP server, but cron-safe, pipe-friendly, and exit-code-correct.
Stop grunt execution with an error message and exit code of choice.
If the async function fails, set the process exit code to 1 and output the error to stderr
when you want to fire an event no matter how a process exits.
Async child process manager providing access to exit code and stdout/stderr
Stream live travis test results of the current commit to your terminal. Exits with the proper exit code too!
Scan a user's NPM tokens and profile and fail with exit code 1 if any fail to comply with policy.
A distributed task cache for shell commands and Nx tasks. Hashes your source files and the lockfile, then replays the cached stdout/stderr/exit code on a hit so the task never runs twice for the same inputs.
Execute a command inside a sprite and return the output with exit code
Commonly used exit codes for usage in applications.
Exit codes for process termination
Point-and-shoot ZAP CLI: deterministic Automation Framework runs against a digest-pinned OWASP ZAP image, stable artifact contract, stable exit codes.
utility that renders information into a string suitable to be embedded in the shell prompt.
pq-cli — Shared clap CLI scaffolding for the pq__ suite: command() scaffolding, sysexits exit-code constants (USAGE=64..IOERR=74), clap_complete completions (incl. nushell), friendly-error -> exit-code rendering. Factored from pqgd-rs's mature CLI; adopted by pqsn-rs at its Gate 5.
Compiles shell commands in .md files into Bash scripts for testing
Unified TUI search over local coding agent histories
Library crate for nils-common in the nils-cli workspace.
Fan stdin out to N concurrent shell-spawned children — a Rust port of moreutils `pee` with strict-compat mode, exit-code aggregation (Default max / Strict bitwise OR), backpressure-paced byte-perfect delivery, and a typed library API.
Command-line driver for POUNCE — solves built-in TNLPs and AMPL .nl files.
A tiny cross-platform library containing exit status and code types
Exit codes for programs
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
Terminal exit codes for humans and machines
tests strings of Ruby code for unauthorized patterns (exit, eval, ...)
a simple conary proxy that masks poor exit codes. See http://docs.rpath.com for more information about conary.
Unlike Open3, Wopen3 does not throw away the exit code of the executed (grandchild) process. Only a child process is spawned and the exit status is returned in $? as normal.
With the help of Open3 executes bash command and conveniently returns its output and exit code
A base class for command line applications doing options parsing and generating exit codes.
Uses pipes to re-raise exceptions. Something better than an exit code has to exist.
AttemptTo calls a code block and re-tries it if it throws an exception. Otherwise exits
rspec-exit_guard guards your test suite against accidental termination caused by exit, abort, or similar calls in the code under test. Instead of letting the process exit (potentially silently, with a passing status), it catches those calls and turns them into test failures.
Execute shell commands and easily get stdout, stderr, exit code, and more
Glint is a library which allows you to fire arbitrary server processes programatically and ensures the processes are shutdown when your code exit
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.