johnkpaul/requireify — pull request #5 by topcloud (2013-12-07 00:30:11+00:00)
Title: Made some changes to test so that issue4 can be observed

Ok, this should explain issue #4:
(it's quite complicated so hopefully, I make sense):

Issue #4 only occurred using the version of requireify from npm install (not when cloned from git). I think the reason for this is because my (default) configuration of git on Windows automatically converts the newlines \n to \r and thus the issue did not show up!

So, to make the git and npm versions consistent on Windows, I changed lines 9 and 10 to also match \r characters.

The odd thing is that if I had left the lines 9 and 10 as they were before, it would actually run well for me and without the parse error!! (again only because I cloned the source from git and my \n got replaced with \r).

Another important thing to note is that when I pulled the branch test-for-issue4, the files last-char-curly-brace.js and a.js both had a pending newline at the end so that might explain why the error did not occur in Linux.

Hopefully these changes should show the error on all operating systems!