A cross platformenv-variable for browsers and node. Of course, browsersdoesn't have environment variables but we do have hashtags and localStoragewhich we will use as fallback.
This is a really easy way of adding some trigger some environment variables thatyou might use for debugging. We assume that the hashtag (#) containsa query string who's key is the name and the value.. the value.
If you want more persisting env variables you can set a query string of envvariables in localStorage. It will attempt to use theenv variable.
This module is written for node and browserify and can be installed using npm:
npm install --save env-variable
This module exposes a node /module.exports interface.
varenv=require('env-variable')();As you can see from the example above we execute the required module. You canalternately store it but I don't assume this a common pattern. When you executethe function it returns an object with all the env variables.
When you execute the function you can alternately pass it an object which willbe seen as the default env variables and all fallbacks andprocess.env will bemerged in to this object.
varenv=require('env-variable')({foo:'bar',NODE_ENV:'production'});Oh, inenv-variable we don't really care how you write your env variables. Weautomatically add an extra lower case version of the variables so you can accesseverything in one consistent way.
And that's basically everything you need to know.random high fives.
MIT