Register tasks to perform when the process exits.
Execute a function on exit without leaking memory, allowing all objects to be garbage collected
Gracefully restore the CLI cursor on exit
Register sync teardown handlers for a resource
Provides a way to execute asynchronous operations before exiting
Create a symlink/copy mount of a project directory with .agentignore/.agentreadonly semantics, then launch a CLI inside it and sync writable changes back on exit
Toggle Pi session persistence mid-session (delete session file on exit)
Spawn or fork a child process with a promise property resolved on exit with stdout, stderr and code.
Gracefully restore the CLI cursor on exit
Ensure child processes are closed when the parent closes
A modal triggered on exit.
Run a command with Docker Compose services started up first, then tear them down on exit. Available as both a CLI (`composed`) and a programmatic API.
A replacement for process.exit that ensures stdio are fully drained before exiting.
Clean spawned child process on exit
when you want to fire an event no matter how a process exits.
```shell TESTNETS_ANVIL_NO_STORAGE_CACHING=1 # run without anvil cache (slower but more deterministic) TESTNETS_ANVIL_VERBOSE=1 # enable anvil logs TESTNETS_ANVIL_KEEP_ALIVE_ON_EXIT=1 # do not kill anvil on exit. Allows debugging the state of node when te
Execute a function on exit without leaking memory, allowing all objects to be garbage collected
Print a copyable Pi resume command when an interactive Pi session exits.
A replacement for process.exit that ensures stdio are fully drained before exiting.
Run some code when the process exits (supports async hooks and pm2 clustering)
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
safely cleanup in signal handlers
[DepUp] Gracefully restore the CLI cursor on exit
A Tailwind CSS plugin for creating beautiful animations.
Rust API for libiperf with live iperf3 metrics export
Extend Bevy buttons with on-entered and on-exited events for press, hover and mouse over states.
Sway IPC daemon
Sway layout and focus helper daemon that adds spiral and stack-main autotiling plus opacity and window renaming.
A simple and extensible state machine implementation in Rust
Sync Taskwarrior tasks with Habitica
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.