Global Define

AMD loader for Node, it creates global define function to provide AMD-style define in node.

TL;DR

// works in node and in a browser (with requirejs)
define([
  'app/models/property',
  'es6!some-module'
], function(Property, someES6Module)
{
  // ...
});

And allows to require modules relative to the basePath (escaping ../../../../.. mess). Combined with support for paths aliases, provides unified environment for modules shared between server and browser (isomorphic javascript).

Note: it exposes global.define method per module (module specific) and only at load time.

Installation

npm install global-define --save

Examples

Basic

Include following line within entry point of your application, and it will automatically add global define function to all included modules/files.

index.js:

require('global-define')({basePath: __dirname});

module.js:

define([
  'app/models/property',
  'app/collections/property_search'
], function(Property, PropertySearch)
{
  // ...
});

Path aliases

Usually its suggested for module id to reflect path to the file, but its not always the case, this is where paths aliases come to help.

In the following example some_module has several components located within lib folder.

index.js:

require('global-define')(
{
  basePath: __dirname,
  paths:
  {
    'some_module/': 'some_module/lib/'
  }
});

node_modules/some_module/lib/component.js:

define('some_module/component', [
  'some_module/another_component'
], function(Dependency)
{
  // ...
});

Black List

If certain modules don't play nice with global define on the server, its possible to exclude them from the world of happiness, by adding them to the black list. It supports glob patterns via minimatch module.

Following example will add global define only to the files of the project, without affecting any dependencies.

index.js:

require('global-define')(
{
  basePath:  __dirname,
  blackList: ['node_modules/**']
});

White List

If you want to play safe, you can white list only certain files in the project.

Following example will add global define only to the files in app/shared folder.

index.js:

require('global-define')(
{
  basePath:  __dirname,
  whiteList: ['app/shared/**']
});

Upstream propagation

In some cases your "topmost" module get required by some other module(s) and you'd like to allow modules required from upstream to enjoy benefits of global-define. Main use case is test frameworks, that require you app module on separate branch from your config/test files.

To signal global-define to propagate it's instance upstream, use forceUpstream flag.

test/config.js:

var path = require('path');
require('global-define')(
{
  forceUpstream: true,
  basePath: path.join(__dirname, '..'),
  paths: {'buster-test/': 'buster-test/lib/'},
});

Expose AMDefine

By default it creates only global define function, so UMD modules still opt-in for server-side way of doing things (some of them are using UMD not only for loading resources, but to choose between browser/server branches of the code).

If you don't have such modules (or blacklisted them) and you need better requirejs/amdefine support, set exposeAmdefine to true, to expose .amd and .require properties of the amdefine module on per file basis.

index.js:

require('global-define')(
{
  basePath:  __dirname,
  blackList: ['node_modules/sinon/'],
  exposeAmdefine: true
});

Invasive Mode

Some instrumentation libraries (e.g. istanbul) break standard loading procedure and go around normal (loading extensions) way. To allow global-define work with files loaded that (manual) way, use invasive mode (overrides Module._compile method) and injects global.define before compilation step.

Note: Most likely you don't need this option, unless you're doing some kind of instrumentation, with one of such libraries.

index.js:

require('global-define')(
{
  basePath:  __dirname,
  invasiveMode: true
});

Alias Require

Some (isomorphic/universal) modules expected to work only when treated with a packaging solution (e.g. webpack), and rely on the bundler to resolve the paths passed to the require function (require('app/router')). To combat this issue while running it in node (i.e. for unit testing purposes), use aliasRequire flag.

index.js:

require('global-define')(
{
  basePath:  __dirname,
  aliasRequire: true,

  paths:
  {
    'chart.js'             : 'empty:', // will return empty object
    'custom-scoped-module' : 'node_modules/@npmcorp/custom-scoped-module/index.js',
    'app'                  : path.join(__dirname, 'app') // will search for under `app` folder
  }
});

Same file invocation

If you want to use global-define within the entry point of your application (your index file). It returns reference to the define function tailored for the invoking module:

index.js:

var define = require('global-define')({basePath: __dirname});

define(['app/lib/helper'], function(Helper)
{
  // ...
});

disableCache (default: false)

This allows you to pass in a boolean to disable caching of the modules that you are requiring from require.cache. This might be useful in development for making changes without having to restart your node server. Please use it with caution, this approach is prone to unforeseen side effects.

index.js

require('global-define')(
{
  basePath:  __dirname,
  disableCache: true
});

Notes

• Uses amdefine under the hood.
• Supports nesting with different configurations.
• Supports CommonJS requirement of the modules using global-define internally.