Execute promises before exiting a process
when you want to fire an event no matter how a process exits.
Run a child as if it's the foreground process. Give it stdio. Exit when it exits.
A Tailwind CSS plugin for creating beautiful animations.
wait-on is a cross platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become available
A replacement for process.exit that ensures stdio are fully drained before exiting.
Execute a function on exit without leaking memory, allowing all objects to be garbage collected
Run some code when the process exits (supports async hooks and pm2 clustering)
Run some code when the process exits
safely cleanup in signal handlers
A replacement for process.exit that ensures stdio are fully drained before exiting.
exiting a node.js process *and flushing stdout and stderr*
Type-safe CLI library / framework with no runtime dependencies
Virtual Environments for Node
Some old grunt utils provided for backwards compatibility.
Execute a function right before the process, or the browser's tab, is about to exit.
Creates a Promise that waits for a single event
Given a response from the npm security api, render it into a variety of security reports
Convert TTF font to WOFF2
unist utility to visit nodes
Exit the process when the `esc` key is pressed
Execute shell command forwarding all stdio.
A graceful way to shutdown / handle process exit
the complete solution for node.js command-line programs
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
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 ;)
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.
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.