We now estimate the resolved module path before resolving using node-resolve to

see if the resolved path matches any file in `options.excludeFiles`;	previously, it was a lot more likely that missing files in the	`excludeFiles` array would throw an error Push to 2.1.4

Author: bminer

lib/moduleConcatStream.js

@@ -202,10 +202,23 @@ class ModuleConcatStream extends Readable {
 opts.excludeNodeModules.indexOf(modulePath) >= 0
 ) )
 {
+// Module is excluded; do not replace
 return match;
 }
 // Get ready to resolve the module
 opts.basedir = path.dirname(filePath);
+/* Take a guess on the resolved path and ignore any modules
+found in `excludeFiles` array */
+let estResolvedPath = modulePath.charAt(0) === "/" ?
+modulePath :
+path.resolve(opts.basedir + "/" + modulePath);
+if(opts.excludeFiles.indexOf(estResolvedPath) >= 0 ||
+opts.extensions.some((ext) =>
+opts.excludeFiles.indexOf(estResolvedPath + ext) >= 0) )
+{
+// File is excluded; do not replace
+return match;
+}
 // Thank you, node-resolve for making this easy!
 try {
 // Resolve the module path
@@ -223,7 +236,9 @@ class ModuleConcatStream extends Readable {
 // Lookup this module's ID
 var index = this._files.indexOf(modulePath);
 if(index < 0) {
-// Not added to project yet; try to add it
+/* Not added to project yet; try to add it after we
+double check to see if we should exclude it or not.
+*/
 if(opts.excludeFiles.indexOf(modulePath) < 0)
 {
 // Not excluded, so we're good to go!

package.json

@@ -1,6 +1,6 @@
 {
 "name": "module-concat",
-"version": "2.1.2",
+"version": "2.1.4",
 "description": "Lightweight CommonJS module concatenation tool",
 "main": "index.js",
 "dependencies": {