Finds the first existing file from a list of choices
Get the first existing path
Finds the first existing file ending with specified extension.
ByteStream is a library making possible to manipulates single bytes and bits on pure JavaScript
extended POSIX-style sprintf
Morph a DOM tree to another DOM tree (no virtual DOM needed)
Storybook Addon A11y: Test UI component compliance with WCAG web accessibility standards
A complete implementation of Protocol Buffers in TypeScript, suitable for web browsers and Node.js.
Synchronous validation of a path existing either as a file or as a directory.
A source map library purpose-build for the Parcel bundler with a focus on fast combining and manipulating of source-maps.
Official React bindings for Redux
The official, opinionated, batteries-included toolset for efficient Redux development
Read text and parse tables from PDF files. Supports tabular data with automatic column detection, and rule-based parsing.
EventEmitter3 focuses on performance while maintaining a Node.js AND browser compatible interface.
React components for Stripe.js and Stripe Elements
Cloud-scale load testing. https://www.artillery.io
Write files in an atomic fashion w/configurable ownership
Infer the owner of a path based on the owner of its nearest existing parent
Octokit authentication strategy for OAuth clients
[](https://www.npmjs.com/package/@aws-sdk/s3-request-presigner) [](https://www.npmjs.com/
This package includes trial watermark webcomponent, that is used by all Ignite UI Web Frameworks.
A global executable to run applications with the ENV variables loaded by dotenv
A library for the MQTT protocol
Performance testing companion for React and React Native
A simple Ruby gem that selects the first existing (non-nil) object in a set of objects.
load the first existing YAML file
Checks against the Pwned Passwords API using the first five characters of the SHA1 hash of a password to determine if it exists in previously disclosed breaches.
The first Ruby package (a.k.a. gem) to exist for making Revolt.chat bots. This project is not officially endorsed by revolt.chat
The first Ruby package (a.k.a. gem) to exist for making Stoat.chat bots and using Stoat.chat webhooks. This project is not officially endorsed by stoat.chat
Cart is framework agnostic solution for shopping cart. There are two existing imlementations. First is *Cart::Simple* which is just basic cart which can store only ID of products without any metadata. The second is *Cart::Advanced* and it is good when you have not just product, but also some metadata as size or color of product etc.
The first Ruby package (a.k.a. gem) to exist for making Fluxer.app bots and using Fluxer.app webhooks. This project is not officially endorsed by Fluxer.app
Cart is framework agnostic solution for shopping cart. There are two existing imlementations. First is *Cart::Simple* which is just basic cart which can store only ID of products without any metadata. The second is *Cart::Advanced* and it is good when you have not just product, but also some metadata as size or color of product etc.
This class provides a Ruby-oriented scheme to safely overwrite an existing file, leaving a backup file unless specified otherwise. It writes a temporary file first, which is renamed to the original file in one action. It accepts a block like some IO class-methods (e.g., each_line) and chaining like String methods (e.g., sub and gsub).
Attest allows you to define spec-like tests inline (within the same file as your actual code) which means almost non-existant overheads to putting some tests around your code. It also tries to not be too prescriptive regarding the 'right' way to test. You want to test private methods - go ahead, access unexposed instance variables - no worries, pending and disabled tests are first class citizens. Don't like the output format, use a different one or write your own. Infact you don't even have to define you tests inline if you prefer the 'traditional' way, separate directory and all. You should be allowed to test your code the way you want to, not the way someone else says you have to!
Deliver all master files managed in a single master snapshot directory into the specified directory while maintaining the hierarchy of the master snapshot directory. If the destination file already exists, back it up first and then deliver the master file. The difference with rsync is that master_delivery creates a symlinks instead of copying the master files. They are symlinks, so you have to keep in mind that you have to keep the master files in the same location, but it also has the advantage that the master file is updated at the same time when you directly make changes to the delivered file. Do you have any experience that the master file is getting old gradually? master_delivery can prevent this. If the master directory is git or svn managed, you can manage revisions of files that are delivered here and there at once with commands like git diff and git commit.
DeprecateSoft is a lightweight Ruby gem that lets you gracefully deprecate methods in your codebase without breaking functionality. It wraps existing instance or class methods and lets you plug in custom before/after hooks for tracking usage via logging, Redis, DataDog, or any other observability tools. Once you verify in your tracking that a method is no longer called, you can remove it safely from your code base. This is especially useful in large codebases where you want to safely remove legacy methods, but first need insight into whether and where they're still being called. Hooks are configured once globally and apply project-wide. Fully compatible with Rails or plain Ruby applications.
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.