fix: module exports

Author: AidasK

bower.json

@@ -1,6 +1,6 @@
 {
   "name": "flow.js",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "main": "src/flow.js",
   "ignore": [
     "**/.*",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "flow.js",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Flow.js library implements html5 file upload and provides multiple simultaneous, stable, fault tolerant and resumable uploads.",
   "main": "src/flow.js",
   "scripts": {

src/flow.js

@@ -1428,16 +1428,27 @@
    * Library version
    * @type {string}
    */
-  Flow.version = '2.0.0';
+  Flow.version = '2.0.1';
 
-  if (typeof module !== 'undefined') {
+  if ( typeof module === "object" && module && typeof module.exports === "object" ) {
+    // Expose Flow 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 = Flow;
-  } else if (typeof define === "function" && define.amd) {
-    // AMD/requirejs: Define the module
-    define(function(){
-      return Flow;
-    });
   } else {
+    // Otherwise expose Flow to the global object as usual
     window.Flow = Flow;
+
+    // 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 flow is used because AMD module names are
+    // derived from file names, and Flow 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 Flow, it will work.
+    if ( typeof define === "function" && define.amd ) {
+      define( "flow", [], function () { return Flow; } );
+    }
   }
 })(window, document);