An opinionated but consistent reducer pattern for organizing data in stores.
Reduce a list of values using promises into a promise for a value
A JavaScript library for efficient immutable updates
higher-order reducer to reset the redux state on certain actions
No description provided.
A family of specs for interoperable TypeScript
append AST into power-assert context
A Redux binding for React Router v4 and v5
reducer for the Shift AST format
React useReducer with async actions
The official runtime utils for Standard Schema
Sequence your effects naturally and purely by returning them from your reducers.
Browser-friendly inheritance fully compatible with standard node.js inherits()
A redux reducer for standard action that merge data to state
Pattern for managing transient local state in redux
Publishing createReducer from https://redux.js.org/recipes/reducing-boilerplate#generating-reducers
An implementation of the WHATWG URL Standard's URL API and parsing machinery
JavaScript Standard Style - ESLint Shareable Config
Reduce any JSON value by traversing depth first and visiting each node
higher-order reducer to ignore redux actions
The standard shareable SCSS config for Stylelint
A performant and standard (Bluebird) library that registers a node-style callback on a promise
utility library for parsing asn1 files for use with browserify-sign.
[](https://github.com/conorhastings/react-syntax-highlighter/actions) [
Make utf8_enforcer to be applied only for non-standards-complying browsers.
Ruby coding standard focused on reducing unnecessary changes, consistency, and developer's happiness.
Reads files stored on Google Cloud Storage (Standard, Durable Reduced Availability or Nearline)
Reduces the output from the standard Minitest run.
VAT rates (standard, reduced, super-reduced, parking) for 45 European countries — EU-27 plus Norway, Switzerland, UK, and more. Includes eu_member flag, local VAT name and abbreviation. Useful for billing, invoicing, e-commerce, fintech, and VAT compliance. From vatnode.dev — live VIES validation via API.
Extends standard Enumerator with a "enumerate_yields" method. Just add a one-liner piece of code to your yield method and your method can be called with or without a block. Recursion and some meta-magic greatly reduce coding.
qdfca (Quick-Deploy Formal Concept Analysis) is a command-line filter that implements Formal Concept Analysis (FCA). It is small, scriptable, and easy to install, with no external requirements other than the standard Ruby library. The input is a formal context in CSV table format. The output is a dot format digraph rendering of the concept lattice with reduced labelling.
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.
Contentful API wrapper library exposing an ActiveRecord-like interface