Gracefully stop hapi.js servers
A replacement for process.exit that ensures stdio are fully drained before exiting.
A replacement for process.exit that ensures stdio are fully drained before exiting.
installs custom cleanup handlers that run on exiting node
exiting a node.js process *and flushing stdout and stderr*
Utility to help find out why Node isn't exiting
Provides a way to execute asynchronous operations before exiting
An isomorphic setImmediate implementation that doesn't prevent the process from exiting naturally.
A replacement for process.exit that ensures stdio are fully drained before exiting
Allow Jasmine tests to "fail-fast", exiting on the first failure instead of running all tests no matter what.
A wrapper around the node.js spawn function providing a promise and graceful exiting
Patch for assuring that winston log messages are written to file before exiting
Cordova plugin for exiting the app programmatically for Android, iOS and WP
A React Native package for gracefully exiting Expo applications
Notifies your app when the user is exiting.
Allow Protractor tests to "fail-fast", exiting on the first failure instead of running all tests no matter what. This can save a great deal of time as Protractor tests are typically slow and expensive.
Effortless React animations for entering, exiting, and updating elements
A small module for exiting a node process cleanly, with ease.
Prevent a process from exiting.
Run some code when the process exits
Execute promises before exiting a process
Allow Jasmine tests to "fail-fast", exiting on the first failure instead of running all tests no matter what.
> Use the https://npm.im/ink react renderer to manage exiting processes.
A library that assists the ljswitchboard in managing multiple windows and exiting when they are all closed.
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
Global, no_std-compatible destructors for all platforms that run after main (like C/C++ __attribute__((destructor)))
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.
Terminal exit codes for humans and machines
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 ;)
omg_kitties enables an innovative new way to exit any and all Ruby scripts. Intstead of typing the boring old `exit`, you can now achieve the same effect in a more semantically-loaded way by typing `omg! kitties!`
Detect if IP belongs to TOR
return_bang implements non-local exits for methods. As a bonus, you also get exception handling that ignores standard Ruby's inflexible begin; rescue; ensure; end syntax. Use return_bang to exit back to a processing loop from deeply nested code, or just to confound your enemies *and* your friends! What could possibly go wrong?
Visualize commands exit status and report the given up commands on the end.
No description provided.
No description provided.
No description provided.