Set $NODE_ENV to "development" works best with mocha --require=env-development
Loads environment variables from `.env.[development|test|production][.local]` files
Easy Webpack configuration function for env-development
``` bespoak [--env development] COMMAND
Loads environment variables from `.env.[development|test|production][.local]` files
Loads environment variables from `.env.[development|test|production][.local]` files
Loads environment variables from `.env.[development|test|production][.local]` files
A library for obtaining browser versions with their maximum supported Baseline feature set and Widely Available status.
A secure webpack plugin that gives the ability to access environment variables via `process.env.*` defined in your `.env[.development|production].toml` files within your web applications built with webpack.
Express server with dynamic template capability, with environment variables env='development' or import the object user startServer method.
Next.js Runtime Environment Configuration - Populates your environment at runtime rather than build time.
A Babel preset for each environment.
`unenv` is a framework-agnostic system that allows converting JavaScript code to be platform agnostic and work in any environment including Browsers, Workers, Node.js, or JavaScript runtime.
Offers getProxyForUrl to get the proxy URL for a URL, respecting the *_PROXY (e.g. HTTP_PROXY) and NO_PROXY environment variables.
AWS credential provider that sources credentials from known environment variables
Robust Environment Configuration for Universal Applications.
Runtime agnostic JS utils
Restrict inputs to certain valid characters (e.g. formatting phone or card numbers)
Use Environment Variables in String
Run scripts that set and use environment variables across platforms
The Vercel Blob JavaScript API client
Next.js dotenv file loading
A module for loading .env files and optionally loading defaults and a schema for validating all values are present.
Loads environment variables from .env file
A tool to containerify your code and application for simple creation of runtime environment locally
catches emails generated in the developer environment and sends them to the ENV['DEVELOPER_EMAIL'] address instead
*Insecure* command line tool to help with developing Shopify themes. Provides simple commands to download, upload and delete files from a theme. Also includes the watch command to watch a directory and upload files as they change. (Dev env only!)
Makes ENV vars easier to keep track of in distributed development
This gem aims to load config to ENV varaible easily. Currently configuration can be done by a .env, a yaml file or by loading from AWS System Manager Parameter Store which is recommended for production deployment.
Log in by typing myproject.local/dev/log_in/john or myproject.local/dev/log_in/admin to easily switch between users in development env
Simple development flow helper that disables development.log, adds STDOUT logging instead, loads .env
Ruby on Rails engine to easily add values to ENV from a configuration yaml file
An encapsulation of a convention I have been using with the slop, nenv, inifile and configatron gems for quick and dirty development of command-line based utility programs. Slop parses ARGV; Nenv parses ENV; inifile parses INI; Configatron keeps it all together. YAML and ERB preprocessing is also available. Ruby configuration files are also supported. and you can specify multiple config files of mixed types at once.
ASCM reads ENV varaibles into a class, providing methods to ensure a setting is available, and mapping variables using Lambdas. The result is a clean, comprehensive configuration file that may be documented as desired, allowing other developers to quickly inspect and understand existing parameters and quickly adding new ones.
Pure Rack middleware that reads forward-auth headers (Remote-User, Remote-Email, Remote-Groups, Remote-Name) and exposes parsed user attributes in the Rack env. Includes a test stub for development environments. No Rails dependency.
vcvars locates a Visual Studio / Build Tools install via vswhere and loads the MSVC toolchain (vcvars*.bat) into the current process, so C extensions build under an mswin Ruby without first opening a "Developer Command Prompt". It provides a library API (Vcvars.activate!), a Rake integration (require "vcvars/rake"), a `vcvars exec -- <cmd>` runner, a `vcvars doctor` that diagnoses the classic MSVC extension-build failures, a `vcvars env` shell-env emitter, and a `vcvars new` scaffolder for MSVC-ready extension gems. It is "ridk enable", but for MSVC. Pure Ruby, no compiler required to install.
No description provided.
No description provided.
No description provided.
No description provided.