Fix aggressive regex matching

[kfitzgerald]

Fixes the include regex pattern includeRegExp being too aggressive, and would match the last instance of , {, which, in a JavaScript context, can be problematic.

Live Examples:

• Previous (too aggressive): http://www.regexr.com/3aj2n
• Fixed: http://www.regexr.com/3aj2k

Fixes the Following Error

stream.js:94
      throw er; // Unhandled stream error in pipe.
            ^
Error: ENOENT, no such file or directory '/Users/kfitzgerald/Repositories/my-repo/))'

Notice the file name, which is: ))

Also included in this PR is a unit test, to help make sure that the pattern continues to cover this scenario.

[coveralls]

Coverage remained the same at 97.75% when pulling f16b14a on kfitzgerald:fix-aggressive-regex-match into e44ee9f on coderhaoxin:master.

[haoxins]

land b4acc0a