Universal Module Definition for use in automated build systems
simple synchronous wrapping of a string return style module supportCommonJS support prevents internal UMDs from conflicting
In order for the UMD wrapper to work the source code for your module shouldreturn the export, e.g.
function method ( ) { //code } method . helper = function ( ) { //code } return method ; For examples, see the examples directory. The CommonJS module format is also supported by passing true as the second argument to methods.
options:
commonJS (default:false) - If commonJS istrue then it will accept CommonJS source instead of source code whichreturns the module.umd(name, source, [options]) Thename should the the name of the module. Use a string like name, all lower case with hyphens instead of spaces.
Ifsource should be a string, that is wrapped in umd and returned as a string.
umd.prelude(module, [options]) return the text which will be inserted before a module.
umd.postlude(module, [options]) return the text which will be inserted after a module.
Usage: umd <name> <source> <destination> [options]Pipe Usage: umd <name> [options] < source > destinationOptions: -h --help Display usage information -c --commonJS Use CommonJS module formatYou can easilly pipe unix commands together like:
cat my - module . js | umd my - module | uglify - js > my - module . umd . min . js Name Casing and Characters Thename passed toumd will be converted to camel case (my-library becomesmyLibrary) and may only contain:
alphanumeric characters $ _ The name may not begin with a number. Invalid characters will be stripped.
MIT
