Require specific environment variables. If they don't exist, the application exits
Easily require environment variables or else
Require environment variables from your npm scripts with a self evident error message
Utility library to load and require environment variables to be set
Simple npm package to require environment variables
Metapackage which bundles opentelemetry node core and contrib instrumentations
A library for Expo config plugins
Wrap all spawned Node.js child processes by adding environs and arguments ahead of the main JavaScript file argument.
AWS credential provider that sources credentials from a Node.JS environment.
Use env() variables in CSS
Inline environment variables.
Use `webpack-bundle-analyzer` in your Next.js project
Global HTTP/HTTPS proxy configurable using environment variables.
Workflow Observability UI
Collects Git commit info from CI or from CLI
Load environment variables from .env and ensure they are defined
Offers getProxyForUrl to get the proxy URL for a URL, respecting the *_PROXY (e.g. HTTP_PROXY) and NO_PROXY environment variables.
Datadog CI plugin for `sbom` commands
Global identifiers from different JavaScript environments
Run scripts that set and use environment variables across platforms
Datadog CI plugin for `sarif` commands
AWS X-Ray Patcher for MySQL (Javascript)
Twilio SendGrid NodeJS mail service
Application that yada yada yada.
Storing configuration in the environment is one of the tenets of a twelve-factor app. However, problems arise when required environment variables aren't set.
Creates a STRICT_ENV constant that you can query for environment variables and get meaningful exceptions
In certain situations it makes sense to allow default values of environment variables that are otherwise required. For example, imagine we're precompiling assets as part of CI when we don't have access to some environment variables we require for the app be up and accepting requests, but aren't required for asset compilation. Using this library we can designate it safe to use default values in those situations.
Validates environment variables requirements with a schema and gives access to their coerced values.
EnvCheck is a lightweight Ruby gem that ensures your required and optional environment variables are present and valid before your app boots. Features smart config discovery (.env_check.yml or config/env_check.yml), comprehensive type validation with 9 built-in validators, .env loading with dotenv, and professional CLI tools. Framework-agnostic design works with Rails 7.1+ through Rails 8.0+, Ruby 3.0+.
Configure required environment variables in your Rails apps
Define environment variable schemas with type casting, required/optional flags, and defaults. Validates at boot time and provides typed accessors.
Load environment variables from multiple .env files with configurable precedence, type coercion, required key validation, default values, and template generation for documentation.
Provides setup information, including environment variables and certificates, required to access services provided by ADB/CDK.
Simple Constnt Configuration for Ruby. Allows you to define configuration CONSTANTS that take values from environment variables. With support for default values, required variables and type conversions.
Hood gives you a standard way to define environment variable requirements for your app.
Manages defining optional (and default) values, environment specific values and required values. There is a focus on 12 Factor principle and definining most variables outside of the environment in production but making it easy for developers to get started with development environment specific variables and sensible defaults.