a tiny module to require all file at one dir
A tiny invariant function
A tiny warning function
Tiny Casing utils
A fast, lightweight LRU (Least Recently Used) cache for JavaScript with O(1) operations and optional TTL support.
a tiny JavaScript expression parser
Fully type-checked EventEmitter
High performance (de)compression in an 8kB package
Super-tiny implementations of some basic hash functions
Tiny and extremely fast globbing
Tiny CBOR library
A minimal fork of nanospy, with more features
An optimised way to copy'ing an object. A small and simple integration
A tiny cookie manipulation plugin
Tiny JavaScript tokenizer.
A tiny but mighty list virtualization component, with zero dependencies 💪
A tiny inflate implementation
An absurdly small JSONC parser.
A library for performing elliptic curve operations on the secp256k1 curve. It is designed to integrate into the BitcoinJS & BitcoinerLAB ecosystems and uses the audited noble-secp256k1 library. It is compatible with environments that do not support WASM,
JSON Merge Patch (RFC 7396) Implementation
Browser-side SDF font generator
A tiny function for truncating a string which may containg ANSI escapes, with automatic terminal width detection.
A BIP32 compatible library
A simple and highly customizable popover react higher order component with no other dependencies!
A tiny framework built on top of Rails in order to help developers focus on writing important business logic. It should be used with hotwired
What is send? ============= It’s a tiny wee ruby gem that is a fork of [Object#try](http://ozmm.org/posts/try.html) and [Object#try from Rails](http://api.rubyonrails.org/classes/Object.html#M000027). It will *never* throw a NoMethodError (no matter the receiver), and returns nil if called on a nil-class or if the method in the receiver does not exist. Note on Patches/Pull Requests ----------------------------- 1. [Fork me!](http://github.com/Burgestrand/send-/fork) 2. Write tests for your new feature or bug fix (important, I don’t want to break your stuff in a future update by accident!) 3. Hack away on the code; make your tests pass. 4. Commit! Don’t touch Rakefile, version or git history in any of the commits you want me to pick. 5. ??? 6. Send me a pull request!
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.