document the npm scoped config option

Author: Bret Ikehara

README.md

@@ -67,7 +67,8 @@ gulpLoadPlugins({
     lazy: true, // whether the plugins should be lazy loaded on demand
     rename: {}, // a mapping of plugins to rename
     renameFn: function (name) { ... }, // a function to handle the renaming of plugins (the default works)
-    postRequireTransforms: {} // see documentation below
+    postRequireTransforms: {}, // see documentation below
+    scoped: true // loads all npm scopes like non-scoped packages
 });
 ```
 
@@ -136,12 +137,22 @@ Note that if you specify the `renameFn` options with your own custom rename func
 
 ## npm Scopes
 
-`gulp-load-plugins` comes with [npm scope](https://docs.npmjs.com/misc/scope) support. The major difference is that scoped plugins are accessible through an object on `plugins` that represents the scope. For example, if the plugin is `@myco/gulp-test-plugin` then you can access the plugin as shown in the following example:
+`gulp-load-plugins` comes with [npm scope](https://docs.npmjs.com/misc/scope) support. By default, the scoped plugins are accessible through an object on `plugins` that represents the scope. When `scoped = false`, the plugins are availble in the top level just like any other non-scoped plugins.
+
+For example, if the plugin is `@myco/gulp-test-plugin` then you can access the plugin as shown in the following example:
 
 ```js
-var plugins = require('gulp-load-plugins')();
+var scoped = require('gulp-load-plugins')({
+  scoped: true,
+});
+
+scoped.myco.testPlugin();
+
+var nonScoped = require('gulp-load-plugins')({
+  scoped: false,
+});
 
-plugins.myco.testPlugin();
+nonScoped.testPlugin();
 ```
 
 ## Lazy Loading

package.json

@@ -34,7 +34,8 @@
     "Carlos Henrique",
     "iamfrontender <iamfrontender@gmail.com>",
     "Brian Woodward",
-    "Zach Schnackel <info@zslabs.com>"
+    "Zach Schnackel <info@zslabs.com>",
+    "Bret K. Ikehara <bret.k.ikehara@gmail.com>"
   ],
   "dependencies": {
     "array-unique": "^0.2.1",