A React context wrapper which lets you get context by name.
Compile regular expressions using named groups to ES5.
Compile regular expressions using duplicate named groups to index-based groups.
Decode named character references
Regex template tag with extended syntax, context-aware interpolation, and always-on best practices
A list of color names and its values
sql named placeholders to unnamed compiler
Lexes CommonJS modules, returning their named exports metadata
No description provided.
Provides a helper function to expand a path to a normalized absolute path. This function also expands dot, tilde, and tilde plus when used as the first path segment.
No description provided.
Extended regular expressions
OpenTelemetry AsyncLocalStorage-based Context Manager
A WebdriverIO plugin. Adapter for Mocha testing framework.
Babel plugin for preserving exports order across transforms
Fastest HTML entities encode/decode library.
No description provided.
A helper function to resolve a module name or path in relation to the specified context and require it.
Register named callbacks and call them with arguments.
Sentry Node-Core SDK
Verifiable Credentials Contexts for JavaScript
Provide context info for eslint-plugin-import-x, so no extra arguments need to be added.
No description provided.
Read named SQL statements from .sql files. Also named parameters for prepared statements.
Context sensitive notifications for Rails.
Uses the actual JavaScript implementation of Handlebars, but supports using Ruby objects as template contexts and Ruby procs as view functions and named helpers
Out of the box, Rails will render templates in a controller context only. This gem allows for calling "render" from anywhere: models, background jobs, rake tasks, you name it.
Uses the actual JavaScript implementation of Handlebars, but supports using Ruby objects as template contexts and Ruby procs as view functions and named helpers
Uses the actual JavaScript implementation of Handlebars, but supports using Ruby objects as template contexts and Ruby procs as view functions and named helpers
Uses the actual JavaScript implementation of walrus.js, but supports using Ruby objects as template contexts and Ruby procs as view functions and named helpers
Out of the box, Rails will render templates in a controller context only. This gem allows for calling "render" from anywhere: models, background jobs, rake tasks, you name it.
Toolkit for rapid prototyping of interactors, use cases and service objects. Using DCI (Data, context and interaction) the new programming paradigm from the inventor of the MVC pattern. This implementation consumes excessive memory (hence the name) and is not recommended for production.
This is a TeX-to-HTML+MathML+CSS converter class using the Javascript-based KaTeX, interpreted by one of the Javascript engines supported by ExecJS. The intended purpose is to eliminate the need for math-rendering Javascript in the client's HTML browser. Therefore the name: SsKaTeX means Server-side KaTeX. Javascript execution context initialization can be done once and then reused for formula renderings with the same general configuration. As a result, the performance is reasonable. The configuration supports arbitrary locations of the external file katex.min.js as well as custom Javascript for pre- and postprocessing. For that reason, the configuration must not be left to untrusted users.
abstract_feature_branch is a Ruby gem that provides a unique variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler to enhance team productivity and improve software fault tolerance. It provides the ability to wrap blocks of code with an abstract feature branch name, and then specify in a configuration file which features to be switched on or off. The goal is to build out upcoming features in the same source code repository branch (i.e. Continuous Integration and Trunk-Based Development), regardless of whether all are completed by the next release date or not, thus increasing team productivity by preventing integration delays. Developers then disable in-progress features until they are ready to be switched on in production, yet enable them locally and in staging environments for in-progress testing. This gives developers the added benefit of being able to switch a feature off after release should big problems arise for a high risk feature. abstract_feature_branch additionally supports Domain Driven Design's pattern of Bounded Contexts by allowing developers to configure context-specific feature files if needed. abstract_feature_branch is one of the simplest and most minimalistic "Feature Flags" Ruby gems out there as it enables you to get started very quickly by simply leveraging YAML files without having to set up a data store if you do not need it (albeit, you also have the option to use Redis as a very fast in-memory data store).
This little module (and attendant command line tool and rackup app) exists for the purpose of providing rudimentary access control to a website when the prospective users are both small in number, and very busy. It circumvents schmucking around provisioning passwords by generating a link which you can pass to each of your users through some other mechanism, that when visited logs them in and keeps them logged in as long as you want. This is basically the equivalent of having a "forgot password" link without anybody having to click on "forgot password", and is perfectly adequate security in certain contexts, namely the ones the author of this gem is interested in.
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.