A replacement for process.exit that ensures stdio are fully drained before exiting.
Cleanly exit process on EPIPE
Execute a function on exit without leaking memory, allowing all objects to be garbage collected
Gracefully restore the CLI cursor on exit
Execute a function right before the process, or the browser's tab, is about to exit.
TypeScript definitions for exit
Enter/exit a state
TypeScript definitions for async-exit-hook
Run a child as if it's the foreground process. Give it stdio. Exit when it exits.
A React Hook to handle exit intent strategies
Exit the process when the `esc` key is pressed
Exit your process, gracefully (if possible)
Catch Node.js exit conditions, including errors and unhandled rejections.
Exit,close,kill,shutdown app completely for React Native on iOS and Android.
Utils to make a Changesets repo enter and exit pre mode
graceful exit process even parent exit on SIGKILL.
markdown-exit integration for shiki
log-update fork that uses async-exit-hook internally
when you want to fire an event no matter how a process exits.
A graceful way to shutdown / handle process exit
Graceful exit for your fastify application
Exit / Close / Kill / shutdown your react native app. Does not invoke a crash notification.
Exit intent detection library.
A replacement for process.exit that ensures stdio are fully drained before exiting.
Custom exit status codes with ? in main
A POSIX sh-compatible shell written in Rust
Tools for managing Amazon S3 objects and buckets
Handle errors and exit in command line programs easily.
Exit QEMU with user-defined code
Exits process with formatted error message. / 输出格式化错误信息并退出进程。
Enables exiting safely with custom exit codes while still calling `Drop` as needed. Aims for minimal magic and maximum flexibilty.
Semantic exit codes inspired by HTTP status codes
Commonly used exit codes for usage in applications.
Hierarchical state machines (statecharts) with a declarative proc macro.
Procedural macro implementation for the hsmc crate.
A minimal actor framework for Rust
Terminal exit codes for humans and machines
Obsolete. Use gem 'Exit_0' instead.
A simple method that runs a child process and raises Exit_0::Non_0 if $?.exitstatus is not zero.
Plugin to make autotest exit after all_good hook. Sometimes I want to just check all my tests, but if there is a failure, I want it to keep running, but if there are no failures, I want it to exit.
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.
Reimplements RSpec's "fail fast" feature for minitest
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.
Execute shell commands with pretty output logging and capture their stdout, stderr and exit status. Redirect stdin, stdout and stderr of each command to a file or a string.
tests strings of Ruby code for unauthorized patterns (exit, eval, ...)
Rack middleware for detecting Tor exits
HospitalPortal::CleanThread provides support for developing threads that exit cleanly. Reliable J2EE deployment requires that all threads started by an application are able to exit cleanly upon request.
Replace all ['yes', 'yeah', 'sure', 'yup'] with 'FUCK YEAH!!!' in whatever files you choose. Do away with code that is less excited than you are ;)
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.
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.