RequireJS and NodeJS support

[stevenvachon]

This is taken from the bottom of jQuery:

if ( typeof module === "object" && module && typeof module.exports === "object" ) {
    // Expose jQuery as module.exports in loaders that implement the Node
    // module pattern (including browserify). Do not create the global, since
    // the user will be storing it themselves locally, and globals are frowned
    // upon in the Node module world.
    module.exports = jQuery;
} else {
    // Register as a named AMD module, since jQuery can be concatenated with other
    // files that may use define, but not via a proper concatenation script that
    // understands anonymous AMD modules. A named AMD is safest and most robust
    // way to register. Lowercase jquery is used because AMD module names are
    // derived from file names, and jQuery is normally delivered in a lowercase
    // file name. Do this after creating the global so that if an AMD module wants
    // to call noConflict to hide this version of jQuery, it will work.
    if ( typeof define === "function" && define.amd ) {
        define( "jquery", [], function () { return jQuery; } );
    }
}

[madrobby]

Hi there! We currently have no plans to add support for loaders that need code changes, mostly because it's a nightmare to support. You can easily add this code on your own if you require it. Note that Zepto doesn't have a noconflict method.

[stevenvachon]

It's a nightmare to support RequireJS? I wouldn't have thought that was the case.

I can't add it myself as this request was in hopes of making my favourite framework even better. Adding it would require others to add it.

[madrobby]

@stevenvachon please see the discussion in #342