Don't flag file as not resolvable too early

[mantoni]

After hours of tracing, I found my bug of the day!

When looking for a package, say ./lib/package.json, the file is sometimes marked as unresolvable, even if ./package.json exists. Whether this works or not depends on the order of fs.readFile yields. The next() implementation already flags the file as unresolvable correctly when there are no directories left to check.

Also, this line causes module-deps to return an empty object with just the __dirname in it, which makes browserify work in this case. However, I have a browserify.transform field in the package.json which is then not present, hence the transform is never invoked.

Maybe you have some idea on how to improve error handling in this case.

[ghost]

Merged in 2.1.1. Thanks for the patch!

[mantoni]

Thanks! Mind bumping the dependency in node-browserify to ~2.1.1? It's currently ~2.0.6 so this fix does not get picked up.