<img src="http://i.imgur.com/ypw29XY.png" align="right"/>
Universal Module Definition for use in automated build systems
return
style module supportIn order for the UMD wrapper to work the source code for your module should return
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 is true
then it will accept CommonJS source instead of source code which return
s the module.The name
should the the name of the module. Use a string like name, all lower case with hyphens instead of spaces.
If source
should be a string, that is wrapped in umd and returned as a string.
return the text which will be inserted before a module.
return the text which will be inserted after a module.
Usage: umd <name> <source> <destination> [options]
Pipe Usage: umd <name> [options] < source > destination
Options:
-h --help Display usage information
-c --commonJS Use CommonJS module format
You can easilly pipe unix commands together like:
cat my-module.js | umd my-module | uglify-js > my-module.umd.min.js
The name
passed to umd
will be converted to camel case (my-library
becomes myLibrary
) and may only contain:
The name may not begin with a number. Invalid characters will be stripped.
MIT
# umd <img src="http://i.imgur.com/ypw29XY.png" align="right"/> Universal Module Definition for use in automated build systems - simple synchronous wrapping of a string - `return` style module support - CommonJS support - prevents internal UMDs from conflicting [![Build Status](https://img.shields.io/travis/ForbesLindesay/umd/master.svg)](https://travis-ci.org/ForbesLindesay/umd) [![Dependency Status](https://img.shields.io/gemnasium/ForbesLindesay/umd.svg)](https://gemnasium.com/ForbesLindesay/umd) [![NPM version](https://img.shields.io/npm/v/umd.svg)](http://badge.fury.io/js/umd) ## Source Format In order for the UMD wrapper to work the source code for your module should `return` the export, e.g. ```javascript 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. ## API options: - `commonJS` (default: `false`) - If commonJS is `true` then it will accept CommonJS source instead of source code which `return`s the module. ### umd(name, source, [options]) The `name` should the the name of the module. Use a string like name, all lower case with hyphens instead of spaces. If `source` 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. ## Command Line ``` Usage: umd <name> <source> <destination> [options] Pipe Usage: umd <name> [options] < source > destination Options: -h --help Display usage information -c --commonJS Use CommonJS module format ``` You can easilly pipe unix commands together like: ```js cat my-module.js | umd my-module | uglify-js > my-module.umd.min.js ``` ## Name Casing and Characters The `name` passed to `umd` will be converted to camel case (`my-library` becomes `myLibrary`) and may only contain: * alphanumeric characters * $ * _ The name may not begin with a number. Invalid characters will be stripped. ## License MIT
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/node_modules/umd/README.md | |||||
#1 | 18810 | tjuricek |
First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy" the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. |