Just the code. Compress a folder but first removes its dependencies (bower/npm) and git files (optional).
A type-safe marriage of `EventTarget` and `EventEmitter`.
Load the local package.json from either src or dist folder
Check if stdout or stderr is interactive
Fixes stack traces for files with source maps
when you want to fire an event no matter how a process exits.
Parse a JSON string that has git merge conflicts, resolving if possible
Like which(1) unix command. Find the first instance of an executable in the PATH.
Wrap those words. Show them at what columns to start and stop.
richer JavaScript errors
Properly hijack require, i.e., properly define require hooks and customizations
Downloade counter for the swc project
the most correct and second fastest glob implementation in JavaScript
option parsing and help generation
Run a child as if it's the foreground process. Give it stdio. Exit when it exits.
A collection of utility libraries used by other Facebook JS projects
An arbitrary-precision Decimal type for JavaScript.
a simple debounce with no dependencies or crazy defaults
Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.
Vendored dependencies for Victory
Color normalization for React Native.
A port of the Brotli compression algorithm as used in WOFF2
A small JS+SVG library for drawing railroad syntax diagrams.
Telegram Bot API type declarations for grammY
An experimental Object-base Parallel Evaluation Environment.
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.
hello world
Show a popup with one line of code. Perfect for format.js responses, and just in JS too.
Lets you add asssertions to your code, not just your tests, using a very clean and simple syntax
Retry... but only once!
integrate pods in form of prebuilt frameworks conveniently, reducing compile time
Ferro is a small Ruby library on top of Opal that enables an object-oriented programming style for creating code that runs in the webbrowser. No more distractions like HTML and searching for DOM elements, just beautiful and simple Ruby code. Front-End-Ruby-ROcks!
Ruby on Rails Live Reload with just a single line of code - just add the gem to Gemfile.
BrowserWarrior is a Ruby on Rails engine that let you reject your non-modern browser user just one line code
Trying to learn that how to make a gem.
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.