dfkaye/module-define

cross-platform shim for module.define() & importScripts() methods in JavaScript in Node.js or browsers.

Build Status

First repo of mine to do this - http://about.travis-ci.org/docs/user/getting-started/ - really like it so far

module-define

In PROGRESS JavaScript shim for cross-platform module.define() and importScripts() APIs.

describe

See my gist: importScripts proposal

justify

Stop using source transformation tools - they make the problem worse, not better.

Node.js part is boilerplate

The fact that the node test suite runs at all proves the concept that the module.define() and importScripts() boilerplate can be used to import files that don't use the boilerplate themselves (notably, the tape testing package itself), and can be used multiple times, in the same file, mimicking the script concatenation strategy used in browser web applications.

Code noise

• importScripts() paths must either be npm module names or top-directory relative paths.
• module.require() inside the the define callback can use module-relative paths.

Using tape to run tests from the node.js command line.

from node command line

cd ./module-define

any of these commands

npm test
node test/node
node test/node/index
node ./test/node/index.js

Browser tests with testem

I've used QUnit with testem to verify that the module var does not conflict with QUnit's module() function. Investigate the files in test/browser/ for example.

from node command line

cd ./module-define
testem

then open a browser at localhost:7357

or use this to run all browsers testem can find automatically

testem ci

The NPM part

TODO