inject a global variable into a module require() tree
Get the npm global path prefix.
A drop-in replacement for fs, making various improvements.
Require global variables
Global namespace without polluting the global scope
A polyfill for the internal diagnostics_channel module
Resolve any installed ES6 compatible promise
The assert module from Node.js, for the browser.
Easily get the CWD (current working directory) of a project based on package.json, optionally starting from a given path. (node.js/javascript util)
The directory used by npm for globally installed npm modules.
Global HTTP/HTTPS proxy configurable using environment variables.
A Babel plugin to inject imports to core-js@3 polyfills
Require global variables
PostCSS plugin to define global data that will be injected into PostCSS for use in other plugins.
Check if installed by yarn globally without any `fs` calls
Polyfill for Metadata Reflection API
A library for manipulating IPv4 and IPv6 addresses in JavaScript.
Check if your package was installed globally
Global identifiers from different JavaScript environments
Require and resolve global modules like a boss
A cross engine globalThis.
Sometimes you have to do horrible things, like use the global object to share a singleton. Abstract that away, with this!
Determine an app's root path from anywhere inside the app
Native Promise Only: A polyfill for native ES6 Promises **only**, nothing else.
Require 'English.rb' to reference global variables with less cryptic names.
Meta gem to not populate global namespace by requiring currencies gem in gemspec.
Binary Transformer plugin for jpeg optim. Requires jpeg optim to be available via the PATH variable globally
Require by path, Define without key. Permissive towards Sprockets directives and global scope pollution.
Similar to globalize, but uses PostgreSQL's JSONB to store data in a single field. No additional tables required. Very thin abstraction
Easily convert phone number from global to domestic, or vice versa. Require Ruby >= 2.1.
Easily and non-intrusively require files from sub-folders. Without polluting global namespace, or having modules clobber each other, include RequireDir and initialize it to get access to #dir and #dir_r
Symbiont is a cool implementation of proc-objects execution algorithm: in the context of other object, but with the preservation of the closed environment of the proc object and with the ability of control the method dispatch inside it. A proc object is executed in three contexts: in the context of required object, in the context of a closed proc's environment and in the global (Kernel) context.
Extention Module 'called_from' provides called_from() global function which gets filename and line number of caller. In short: require 'called_from' filename, linenum, function = called_from(1) is equivarent to: caller(1)[0] =~ /:(d+)( in `(.*)')?/ filename, linenum, function = $`, $1, $2 But called_from() is much faster than caller()[0].
This generator cross-posts entries to Medium. To work, this script requires a MEDIUM_USER_ID environment variable and a MEDIUM_INTEGRATION_TOKEN. The generator will only pick up posts with the following front matter: `crosspost_to_medium: true` You can control crossposting globally by setting `enabled: true` under the `jekyll-crosspost_to_medium` variable in your Jekyll configuration file. Setting it to false will skip the processing loop entirely which can be useful for local preview builds.
Some projects are confined by regulations (or requirements) that demand data can not be used to identify individuals. In such cases data must be scrubbed i.e. identifiable object names must be removed before unauthorized users can see said data. For example, when a developer needs to recreate a bug on their own system that was reported by a customer using customer-specific data. One method to do this is to use globally unique identifiers within the system to identify any given object.
This generator cross-everything entries to Medium. To work, this script requires a MEDIUM_USER_ID environment variable and a MEDIUM_INTEGRATION_TOKEN, MEDIUM_ENTITY. The generator will only pick up posts with the following front matter: `crosseverything_to_medium: true` You can control crosseverything globally by setting `enabled: true` under the `jekyll-crosserything_to_medium` variable in your Jekyll configuration file. Setting it to false will skip the processing loop entirely which can be useful for local preview builds.