Redis client extensions for CCNQ4
Define a data property on an object. Will fall back to assignment in an engine without descriptors.
An LRU cache of weak references
Smallest positive double-precision floating-point normal number.
This package helps to convert old i18next translation resources to the new i18next v4 json format.
Cloudflare Turnstile integration for React.
See nodejs errors with less clutter
SCSS preset for Storybook
Smallest positive normalized half-precision floating-point number.
Smallest positive normalized single-precision floating-point number.
A collection of probability distribution functions
normal-utils utils
adds the capability to abort/cancel running & pending uploads
Run the supplied function exactly one time (once)
A Test-Anything-Protocol library for JavaScript
Lightning fast normal and incremental md5 for javascript
Simple utility for decoding Rails 4.x sessions in node.js
JSON canonicalize function
Get the PATH environment variable key cross-platform
Normal distribution quantile function.
The Aztec KV store is an implementation of a durable key-value database with a pluggable backend. The only supported backend right now is LMDB by using the [`lmdb-js` package](https://github.com/kriszyp/lmdb-js).
Wraps classes defined in computed keys of other classes affected by https://bugzilla.mozilla.org/show_bug.cgi?id=1887677
PostCSS plugin to fallback initial keyword.
Bugsnag error reporter for browser JavaScript
Normalizes redundand relational data by given keys
Shelvit extends the functionality of Lcsort by cleaning unsortable callnumbers before attempting to normalize them again.
Supports importing data over various transports with key-value remapping & normalization
A persistant, file based hash
SkeletonKey provides deterministic wallet recovery, seed normalization, and key derivation for Bitcoin, Ethereum, and Solana.
Using `has_cache` in your classes provides a `cached` method that allows automatic caching of the result of a method that is normally available on the class, or an instance of the class. It mitigates the hassle of creating and tracking keys as you would with the standard Cache Store interface, by inferring keys from the location `cached` is invoked.
Maps values from hashes with different structures and/or key names. Ideal for normalizing arbitrary data to be consumed by your applications, or to prepare your data for different display formats (ie. json). Tiny module that allows you to easily adapt from one hash structure to another with a simple declarative DSL.
FancyOpenStruct is a subclass of OpenStruct, and is a variant of RecursiveOpenStruct. This allows you to convert nested hashes into a structure where keys and values can be navigated and modified via dot-syntax, like: foo.bar = :something. This particular gem also adds support for Hash methods (such as length or merge), and also allows you to access and modify the data structure the same way that you would handle a normal Hash.
Maps values from hashes with different structures and/or key names. Ideal for normalizing arbitrary data to be consumed by your applications, or to prepare your data for different display formats (ie. json). Tiny module that allows you to easily adapt from one hash structure to another with a simple declarative DSL.
Similar in behavior to Object#presence defined in ActiveSupport, Significance is a state which determines not just the blank-ness of an object but whether or not the non-blank object has any real-world value. The utility of this gem can best be demonstrated when considering the merging of two hashes. Under normal circumstances the mere existence of an equivalent key in the second hash results in its overriding the corresponding value in the original hash. Using Hash#significant_merge, however, the second hash will retain only key-value pairs whose values are "significant," even applying the significance filter recursively into child hashes or arrays.
# Fancy Logger An easily customizable logger with style. ## Install ### Bundler: `gem 'fancy_logger'` ### RubyGems: `gem install fancy_logger` ## Usage Simply use as if you were using the normal Ruby `Logger` class: ```ruby require 'fancy_logger' logger = FancyLogger.new(STDOUT) logger.info "Hello" ``` ### Config The `config` instance method allows you to modify the configuration of the Logger within a DSL. Continuing with our last example: ```ruby logger.config do timestamp_format "%c" styles do info do foreground :yellow blink true end end end logger.debug 'Look here!' logger.info 'Doing things...' logger.warn 'Watch out!' logger.error 'Bad' logger.fatal 'VERY bad' logger.unknown 'Weird unknown stuff' ``` #### Output ![][output_example] ### Config ```ruby # The format of the timestamp in the log. Follows the strftime standards. timestamp_format "%F %r" # On the first logged message, FancyLogger will prepend a help message # containing a list of all the severities (debug, info, warn, etc) styled # according to your config as reference. # You can disable this by setting the below option to false. show_help_message true # Under styles, you have a configuration for each severity. # Each severity has a configuration with the following valid options: # Key: foreground # Value: # :default, :black, :red, :green, :yellow, :blue, :magenta, :cyan, :white # # Key: background # Value: # :default, :black, :red, :green, :yellow, :blue, :magenta, :cyan, :white # # Key: reset # Value: true or false # # Key: bright # Value: true or false # # Key: italic # Value: true or false # # Key: underline # Value: true or false # # Key: # blink # Value: true or false # # Key: inverse # Value: true or false # # Key: hide # Value: true or false styles do debug do foreground :black background :cyan end info do foreground :default background :default end warn do foreground :yellow background :default blink true end error do foreground :red background :default end fatal do foreground :black background :red bold true underline true end unknown do foreground :black background :white underline true end end ``` ## Contributing * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it * Fork the project * Start or switch to a testing/unstable/feature/bugfix branch * Commit and push until you are happy with your contribution * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, VERSION or gemspec. ## Copyright Copyright © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details. [output_example]: http://oi44.tinypic.com/sfwlkp.jpg
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.