For setting a global config object managed as a requirement

Downloads in past


100.3.18 years ago8 years agoMinified + gzip package size for global-configuration in KB


Build Status npm version


Provide what is essentially an explicitly set of frozen global variables which can then be required by any module that needs them.
This can be preferable to having to pass any configuration all the way through your node application, which in turn is usually better than setting global variables.


$ npm install global-configuration


setConfiguration( configuration , options )
import setConfiguration from 'global-configuration/set';

  • configuration whatever you want to be made available when subsequently importing / requiring global-configuration.
  • options object optionally containing the following
- __options.freeze__ _default: true_ - used to prevent the [freezing]( of the configuration object.
- __options.assign__ _default: false_ - causes the passed configuration object to have its properties [assigned]( to the existing configuration, rather than replacing it.
import clearConfiguration from 'global-configuration/clear';

This is a testing utility that removes the existing configuration from the require cache. By calling this, calling setConfiguration(configuration) and then re-requiring any target file, that target file will then be returned from require with the new configuration applied.

Example Usage

Server Side

service.js (initiation of server side process)
import setConfiguration from 'global-configuration/set';
// Assuming ./app here exports an express application.
import MyApplication from './app';

// This should probably be the only place you read in environment vars IMO.
setConfiguration({ foo: 'bar' });

new MyApplication();

appLogic.js (somewhere inside the application) ````js import configuration from 'global-configuration';
function qux() {
qux(); // bar
export default qux;
// If we were to import setConfiguration again and try and set it an error would be thrown: // once set the configuration cannot be changed unless explicitly stated the first time it is called.
// Equally if we were to import configuration before setConfiguration had been called an error would get thrown at compile time. // This (the compile time error) is probably the main reason why this package was written. ````

Client Side

client.js (initiation of client side js, assume compiled via browserify / similar) ````js import React from 'react'; import Page from './page.jsx'; import setConfiguration from 'global-configuration/set';
(function clientJS() {
React.render(<Page/>, document);
}()); ````
component.js (somewhere inside the client side app) ````js import React from 'react'; import configuration from 'global-configuration';
const Component = React.createClass({
render: function render() {
    return (
        <div>{ }</div>
export default Component; ````


gulp/test.js ````js import gulp from 'gulp'; import mocha from 'gulp-mocha'; import setConfiguration from 'global-configuration/set';
setConfiguration({ foo: 'baz' }, { freeze: false });
gulp.task('test', function gulpTest() {
return (
        .src([ 'app/**.test.*' ], { read: false })
}); ````
appLogic.test.js ````js import setConfiguration from 'global-configuration/set'; import clearConfiguration from 'global-configuration/clear'; import assert from 'assert';
describe('appLogic', () => {
it('should return foo from configuration', () => {
    const foos = [ 'alpha', 'beta', 'gamma' ];
    foos.forEach((foo) => {
        // This only works because `freeze: false` was set the first time set was called (in gulp/test.js).
        setConfiguration({ foo: foo });
        const appLogic = require('./appLogic');
        assert(appLogic() === foo);

afterEach(() => {
}); ````