Find all JS files which do not have code coverage
Does this JS environment support the `name` property on functions?
A ridiculously light-weight argument validator (now browser friendly)
smart-buffer is a Buffer wrapper that adds automatic read & write offset tracking, string operations, data insertions, and more.
Parses set-cookie headers into objects
Contains parsers and serializers for ASN.1 (currently BER only)
Utilities for collecting TSConfigs for linting scenarios.
Run an array of functions in parallel
Get an iterator for any JS language value. Works robustly across all environments, all versions.
when you want to fire an event no matter how a process exits.
Webpack loader that resolves relative paths in url() statements based on the original source file
Unique tag for use in the type-fest Tagged type
An implementation of the WHATWG URL Standard's URL API and parsing machinery
Compare items in two sequences to find a longest common subsequence
TypeScript package which smartly trims and strips indentation from multi-line strings
Minimal GraphQL client supporting Node and browsers for scripts or simple apps.
Parses well-formed HTML (meaning all tags closed) into an AST and back. quickly.
Query result type converters for node-postgres
Plain color conversion functions
ProseMirror plugin for cursors at normally impossible-to-reach positions
A system for sharing tool configurations between projects without duplicating config files.
A PNG decoder in JavaScript
Interface used to connect Apollo Gateway to Apollo Server
Compare items in two sequences to find a longest common subsequence
Add clever little base36 codes for your DataMapper and ActiveRecord objects.
TODO
Kills pumas, the code kind
Kills pumas, the code kind
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.
Have fun with the Advent of Code using Ruby.
A wrapper gem for the google directions API
Rails engine & generators for bootstrapping a Hashrocket project
RubyTodo allows you to have in-code todos and scan them to view the todos as a list
Sketches allows you to create and edit Ruby code from the comfort of your editor, while having it safely reloaded in IRB whenever changes to the code are saved.
A bunch of code that I like to have in my Rails apps. Use at your own risk.
This gem provides simple request logging for Grape with just few lines of code you have to put in your project! In return you will get response codes, paths, parameters and more!
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.