Let your JS API users either give you a callback or receive a promise
Call me maybe.
A Node.js module for creating REST clients with easy request model templating and straightforward extensibility
Call me maybe
Call me maybe
An extensible implementation of the Maybe type for functional programming
Fuzzy filtering and string scoring
Transform stream that gunzips its input if it is gzipped and just echoes it if not
Combine 0 or more errors into one
Parse, Resolve, and Dereference JSON Schema $ref pointers
tar-stream is a streaming tar parser and generator and nothing else. It operates purely using streams which means you can easily extract/parse tarballs without ever hitting the file system.
Maybe/Optional type implementation in Typescript. Main motivation for creating this library was handling `null` values in deeply nested data, coming from GraphQL APIs, but the library itself is not limited to GraphQL.
Transform stream that `bzip2`s its input if it is `bzip2`ped and just echoes it if not
Maybe call a callback if it's a function
Implementation of common algebraic types in JavaScript + Flow
Simple, transparent parser combinators toolkit that supports any tokens
Parse, Resolve, and Dereference JSON Schema $ref pointers
Simple reusable React error boundary component
Turn a writable and readable stream into a streams2 duplex stream with support for async initialization and streams1/streams2 input
Transform stream that decompress its input if it's compressed, and echoes it if not
Utility to help find out why Node isn't exiting
Parse, Resolve, and Dereference JSON Schema $ref pointers
Generates and consumes source maps
Common algebraïc data types for JavaScript
Event handler and listener for Ruby
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.