env-wrapper
A simple js wrapper around environmental variables, to allow upfront loading, checking, and defaulting of required variables
- Installation
- Load environment from a file
- Read and enforce that a required environment property is present
- Read and default an optional environment property
- Simple getter / setter
- Testing
- Release History
- License
Installation
From the terminal, install the package from npm:
npm i env-wrapper
From within your code, import the library:
const env =
Load environment from a file
Optionally read key-value pairs from a file and insert them into the environment. If a filename is not given, '.env' in the base directory is used. If either the assumed or named file does not exist, no error is issued. An error will be issued if the file exists but and error in encountered. Note that this is a convenience method, and env-wrapper will readily handle any environment variables inserted through other means.
envenv
Example .env file:
PORT=1234
DATABASE_URL=db://localhost
Read and enforce that a required environment property is present
The original intent of this library was to simply ensure fail-fast behavior if a required environment variable had not been specified, so that we know when the application loads instead of 3am next Tuesday when actually uses it.
const databaseUrl = env
Read and default an optional environment property
If the requested environment property cannot be found, and a default value is specified, that value will be inserted into the environment, and then returned as the requested value. Because the environment can be altered by this form, this can also be used as a shortcut for conditionally priming the environment for later use.
const port = env
Simple getter / setter
The library also provides a simple getter and setter that can be used for unconditionally inserting a value into the environment, or retrieving a value from the environment. Unlike require above, get will either return the found value, or undefined if a value is not found.
envconst key = env
Testing
There are several Jasmine-based unit tests that can be run from the terminal if desired:
npm test
Release History
Version | Changes |
---|---|
1.0.7 | Documentation revamp |
1.0.6 | Fix to handle .env file values with embedded '=' symbols |
1.0.5 | Changed load to sync operation; Fix to path calculations |
1.0.4 | Added load method; moved tests to Jasmine |
1.0.3 | Require method returns value |
1.0.2 | Fix for error message unit test |
1.0.1 | Added set method; fixed package.json NPM error |
1.0.0 | Initial Release |
License
This work is released under the MIT license - see the LICENSE file for details