destroy a stream if possible
Write files in an atomic fashion w/configurable ownership
Read and write files atomically and reliably.
split a Text Stream into a Line Stream, using Stream 3
A simple batching function that allows you to atomically batch a series of operations.
RxJS operator that unsubscribes when Angular component is destroyed
Enable destroying a server, and all currently open connections.
Mimic a Node.js HTTP response stream
Regex template tag with extended syntax, context-aware interpolation, and always-on best practices
Turn a writable and readable stream into a streams2 duplex stream with support for async initialization and streams1/streams2 input
An iteration of the Node.js core streams with a series of improvements
Fast way to write a file atomically, for Node.js
Universal, high-performance JavaScript styles
tsParticles particles destroy updater
Minimal and efficient cross-platform file watching library
Write files in an atomic fashion w/configurable ownership
A tiny Node.js module to make any server force-closeable
Prunes dependencies from your package
TypeScript definitions for destroy
React specific wrapper for the Atomic component library
TypeScript definitions for server-destroy
TypeScript definitions for write-file-atomic
pipe streams together and close all of them if one of them closes
Detects the ALPN protocol
*Atomic archiving/unarchiving for ActiveRecord-based apps* We had the problem that acts_as_paranoid and similar plugins/gems always work on a record by record basis and made it very difficult to restore records atomically (or archive them, for that matter). Because the archive and unarchive methods are in transactions, and every archival record involved gets the same archive number upon archiving, you can easily restore or remove an entire set of records without having to worry about partial deletion or restoration. Additionally, other plugins generally screw with how destroy/delete work. We don't because we actually want to be able to destroy records.
*Atomic archiving/unarchiving for ActiveRecord* acts_as_paranoid and similar plugins/gems work on a record-by-record basis and make it difficult to restore records atomically (or archive them, for that matter). Because ArchivalRecord's #archive! and #unarchive! methods are in transactions, and every archival record involved gets the same archive number upon archiving, you can easily restore or remove an entire set of records without having to worry about partial deletion or restoration. Additionally, other plugins generally change how destroy/delete work. ArchivalRecord does not, and thus one can destroy records like normal.