defuse

defuse

A poor man's module namespacing solution for the browser.

defuse.def('foo.bar', function(exports) {
    exports.baz = function() { return 'qux'; }
});

console.log(defuse.use('foo.bar').baz);

Why?

For simple projects, I sometimes don't need the power offered by module loaders, bundlers or similar tools, and would prefer to just have a way of namespacing the project's modules, as opposed to a complete solution for require()ing and using everything, vendor libraries included.

Browserify is really awesome. My only reason for not using it for every browser-based project is that I have yet to find a way of testing browserified projects using phantomjs. For projects that don't use the DOM, or projects which make sense both in node and the browser, browserify is perfect. The tests can be done from node, and each module to be tested can simply be require()d. Things aren't as simple when phantomjs is involved. Short of writing a very awkward require() utility available in the tests, we need to test each module using the entire browserified bundle. This makes writing tests a bit more difficult, since the stack traces are less useful than if the modules were still separate files.

API

defuse.def(name, loader)

Defines a module.

defuse.def('foo.bar', function(exports) {
    exports.baz = function() { return 'qux'; }
});

defuse.use(name)

Returns a defined.

console.log(defuse.use('foo.bar').baz);

defuse.pollute()

Pollutes the global namespace with def, use and undef. Tucked away in a function to try be slightly less opinionated.

defuse.pollute();

// we can now do this:
def('foo.bar');
use('foo.bar');

defuse.undef(name)

Undefines a module.

defuse.undef('foo.bar');