Validate your env variables using Ajv with .env file support using Node.js built-in parseEnv

Next.js Runtime Environment Configuration - Populates your environment at runtime rather than build time.

Config-as-Code for Neon. Define a `neon.ts` policy and inspect/diff/deploy it against the Neon API as plain TypeScript functions.

Full CSS support for JSX without compromises

Astro integration to use varlock for .env file loading - adds validation, type-safety, and extra security features

Load environment variables from .env files. Decode secret values from AWS Secrets Manager, Google Secret Manager, and other sources.

hydrate environment variables from .env files into process.env

Gatsby uses the phenomenal project [Babel](https://babeljs.io/) to enable support for writing modern JavaScript — while still supporting older browsers. This package contains the default Babel setup for all Gatsby projects.

> Currently an alpha-quality, best-effort implementation. > May be unnecessary if you use TypeScript's `"module": "NodeNext", "moduleResolution": "NodeNext"`

Webpack plugin that allows to configure path or URL for fetching dynamic imports

Environment utilities

Next.js dotenv file loading

Automatically insert live Angular components into a dynamic string of content (based on their selector or any pattern of your choice) and render the result in the DOM.

Fast, expressive styling for React.

Resolve and inject Neon connection strings for the branch selected by your neon.ts policy. fetchEnv / parseEnv plus a `neon-env` CLI with `run` and `export`.

Cross platform environment variables with process.env, window.name, location.hash and localStorage fallbacks

Convert modern CSS into something browsers understand

Load .env into React Native with import statements. A Babel plugin that inlines environment variables at build time.

Loads environment variables from `.env.[development|test|production][.local]` files

Minimalist yEnc and dynEncode encoder and decoder library for browser and NodeJS