Autoload your environment variables from your `.env` file, no code changes required. Similar to `dotenv`, but with zero-dependencies and less verbose.
This packages lets you autoload your environment variables from your .env file, no code changes required.
Similar to dotenv, but with zero-dependencies and less verbose.
Easy as:
yarn add envk
node -r envk index.js
Features:
.env.<NODE_ENV> or .env file.env filename with ENVK environment variable"SECRET=hello\nworld"#You can see what's happening inspecting index.js.
Nothing more, nothing less.
Load envs from .env:
node -r envk index.js
Load envs from .env.production file, otherwise .env:
NODE_ENV=production node -r envk index.js
Load envs from specific file:
ENVK=file.env node -r envk index.js
Log to console imported variables:
ENVK_DEBUG=1 node -r envk index.js
FAQs
Autoload your environment variables from your `.env` file, no code changes required. Similar to `dotenv`, but with zero-dependencies and less verbose.
The npm package envk receives a total of 149 weekly downloads. As such, envk popularity was classified as not popular.
We found that envk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.