umd-util
v2.0.1
Published
Export JavaScript files in UMD (Universal Module Definition) format.
Downloads
25
Maintainers
Readme
umd-util
Export JavaScript files in UMD (Universal Module Definition) format.
Features
- Utility script to export files in UMD format.
- Task managers not required. 😄
This repository provides a simple way to build your files with support for the design and implementation of the Universal Module Definition (UMD) API for JavaScript modules. These are modules which are capable of working everywhere, be it in the client, on the server or elsewhere.
The UMD pattern typically attempts to offer compatibility with the most popular script loaders of the day (e.g RequireJS amongst others). In many cases it uses AMD as a base, with special-casing added to handle CommonJS compatibility.
Variations
Regular Module
amdNodeWeb / returnExports / templates/returnExports.js - Defines a module that works in Node, AMD and browser globals. If you also want to export a global even when AMD is in play (useful if you are loading other scripts that still expect that global), use returnExportsGlobal.js.
amd / templates/amd.js Defines a module that works in AMD.
amdCommonWeb / templates/amdCommonWeb.js Defines a module that works in CommonJS Strict, AMD and browser globals.
amdWeb / templates/amdWeb.js Defines a module that works in AMD and browser globals.
common / templates/common.js Defines a module that works in CommonJS Strict.
node / templates/node.js Defines a module that works in Node.
web / templates/web.js Defines a module that works in browser globals.
See more variation options that can be added as templates onto this project on the UMD (Universal Module Definition) patterns.
Install
Install with npm
$ npm install umd-util
Usage
Build a simple module
Let's wrap src/foo.js
file with UMD definition:
'use strict';
function Foo() {}
Then, in the build script:
const umdify = require('umd-util');
umdify.sync('src/foo.js', {
destination: 'dist'
});
After build dist/foo.js
will look like:
(function(root, factory) {
if (typeof define === 'function' && define.amd) {
define([], factory);
} else if (typeof exports === 'object') {
module.exports = factory();
} else {
root.Foo = factory();
}
}(this, function() {
'use strict';
function Foo() {}
return Foo;
}));
Note that by default the filename foo.js
is uppercased and will be used as the return exports for your module and also for the global namespace, in this case root.Foo
. This is configurable, see the advanced build section below.
Build with dependencies
Let's wrap src/foo.js
file with UMD definition defining some dependencies:
'use strict';
function Foo() {}
Then, in the build script:
const umdify = require('umd-util');
umdify.sync('src/foo.js', {
dependencies: function(file) {
return [
{
name: 'moduleName1',
amd: 'moduleName1_amd',
cjs: 'moduleName1_cjs',
global: 'moduleName1_glob',
param: 'moduleName1'
},
{
name: 'moduleName2',
amd: 'moduleName2_amd',
cjs: 'moduleName2_cjs',
global: 'moduleName2_glob',
param: 'moduleName2'
}
];
},
destination: 'dist'
});
After build dist/foo.js
will look like:
(function(root, factory) {
if (typeof define === 'function' && define.amd) {
define(['moduleName1_amd', 'moduleName2_amd'], factory);
} else if (typeof exports === 'object') {
module.exports = factory(require('moduleName1_cjs'), require('moduleName2_cjs'));
} else {
root.Foo = factory(root.moduleName1_glob, root.moduleName2_glob);
}
}(this, function(moduleName1, moduleName2) {
'use strict';
function Foo() {}
return Foo;
}));
The advanced configuration for the dependencies allows you to have full control of how your UMD wrapper should handle dependency names.
Advanced build
Let's wrap src/foo.js
file with UMD definition and exports the Foo.Bar
class:
'use strict';
function Foo() {};
Foo.Bar = function() {};
Then, in the build script:
const umdify = require('umd-util');
umdify.sync('src/foo.js', {
exports: function(file) {
return 'Foo.Bar';
},
namespace: function(file) {
return 'Foo.Bar';
}
destination: 'dist'
});
After build dist/foo.js
will look like:
(function(root, factory) {
if (typeof define === 'function' && define.amd) {
define([], factory);
} else if (typeof exports === 'object') {
module.exports = factory();
} else {
root.Foo.Bar = factory();
}
}(this, function() {
'use strict';
function Foo() {};
Foo.Bar = function() {};
return Foo.Bar;
}));
Templates
In order to use any of the variations defined on the UMD (Universal Module Definition) patterns repository you can use the following template keys:
<%= amd %>
: Contains the AMD normalized values from the options dependencies array, e.g.['a', 'b']
turns into['a', 'b']
.<%= cjs %>
: Contains the CommonJS normalized values from the options dependencies array, e.g.['a', 'b']
turns intorequire('a'), require('b')
.<%= commaCjs %>
: As above, prefixed with ', ' if not empty.<%= global %>
: Contains the browser globals normalized values from the options dependencies array, e.g.['a', 'b']
turns intoroot.a, root.b
.<%= commaGlobal %>
: As above, prefixed with ', ' if not empty.<%= namespace %>
: The namespace where the exported value is going to be set on the browser, e.g.root.Foo.Bar
.<%= exports %>
: What the module should return, e.g.Foo.Bar
. By default it returns the filename with uppercase without extension, e.g.foo.js
returnsFoo
. If using CommonJS, this value may be an object as specified by the result of options.exports<%= param %>
: Comma seperated list of variable names which are bound to their respective modules, ega, b
.<%= commaParam %>
: As above, prefixed with ', ' if not empty.
You can also use umd-templates, using the patternName.path
property if template
option is used, and patternName.template
if templateSource
is used.
| Like us a lot? Help others know why you like us! Review this package on pkgreview.dev | ➡ | | | ----------------------------------------------------------------------------------------------------------------------------------------- | --- | --------------------------------------------------------------------------------------------------------------------- |
API
umdify(source, options?)
umdify.sync(source, options?)
source
Type: string
Default: none
File to export.
options
Type: object
dependencies
Type: function
Default: function() {
return [];
}
Function which returns an array of dependencies. Each dependency is specified either as a string, or as an object of the form.
{
dependencies: function (file) {
return {
name: 'defaultModuleName',
amd: 'moduleNameInAMD',
cjs: 'moduleNameInCommonJsAndNodeJs',
global: 'moduleNameInBrowserGlobals',
param: 'ModuleIdentifier'
}
}
destination
Type: string
Default: umd
Destination directory.
exports
Type: function
Default: function(file) {
return capitalizeFilename(file);
}
Specifies the item (or for CommonJS, item's) which the module will export. For non CommonJS, this value should be a string specifying the exported item.
{
exports: function (file) {
return 'Foo.Bar';
}
}
For CommonJS, this value should be an object with keys specifying the names and values specifying the exported items.
{
exports: function (file) {
return {
'Foo': 'Foo',
'FooBar': 'Foo.Bar'
};
}
}
namespace
Type: function
Default: function(file) {
return capitalizeFilename(file);
}
Specifies the global namespace to export to. Only used for Web globals.
{
namespace: function (file) {
return 'My.Global.Namespace';
}
}
templateName
Type: string
Default: none
Specifies the name of the template to use. Available template names are amd
, amdNodeWeb
, amdCommonWeb
, amdWeb
, common
, node
, returnExports
and web
. If specified, overrides the template and templateSource.
{
templateName: 'amdNodeWeb'
}
templateSource
Type: string
Default: none
Specifies the lodash template source to use when wrapping input files. If specified, overrides template.
{
templateSource: 'module.exports = <%= exports %>'
}
template
Type: string
Default: path.join(__dirname, 'templates/returnExports.js')
Specifies the path to a file containing a lodash template to use when wrapping input files.
{
template: '/path/to/my/template'
}
License
MIT