3rd-eden / env-variable

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

env-variable

A cross platform env-variable for browsers and node. Of course, browsers doesn't have environment variables but we do have hashtags and localStorage which we will use as fallback.

hashtags

This is a really easy way of adding some trigger some environment variables that you might use for debugging. We assume that the hashtag (#) contains a query string who's key is the name and the value.. the value.

localStorage

If you want more persisting env variables you can set a query string of env variables in localStorage. It will attempt to use the env variable.

Installation

This module is written for node and browserify and can be installed using npm:

npm install --save env-variable

Usage

This module exposes a node / module.exports interface.

var env = require('env-variable')();

As you can see from the example above we execute the required module. You can alternately store it but I don't assume this a common pattern. When you execute the function it returns an object with all the env variables.

When you execute the function you can alternately pass it an object which will be seen as the default env variables and all fallbacks and process.env will be merged in to this object.

var env = require('env-variable')({
  foo: 'bar',
  NODE_ENV: 'production'
});

Oh, in env-variable we don't really care how you write your env variables. We automatically add an extra lower case version of the variables so you can access everything in one consistent way.

And that's basically everything you need to know. random high fives.

License

MIT

env-variable's Issues

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

0.0.4 no longer works in an IFrame with third-party cookies disabled.

If third-party cookies are disabled on Chrome, the following line will throw a DOMException SecurityError:

    if (window.localStorage) {

This should probably be wrapped in a try-catch-block, like in 0.0.3.