ben-ng
Failure to account for backslashes in Windows-paths
Running minifyify on Windows-machines produce sourcemaps with minified sources in sourcesContent and all mappings pointing to 1:0 in the relevant file.
After some sleuthing I've come to the conclusion that the problem originates in line 117 of lib/minifier.js. file is an absolute Windows-path, and is resolved relative to cwd, using path.sep. Thus, all entries in Minifier.registry uses \ as separator.
In line 311, when calling bundleMap.eachMapping in Minifier.prototype.transformMap, the mapping.source received from browserify uses / as a separator and the call to Minifier.fileExists always fails.
This can be fixed by appending .replace(/\\/g, '/') in line 117 (and probably line 45), but the most correct course of action would probably be to find browserify's method of sanitizing the filenames and replicate that, so backslashes in unix-paths doesn't become problematic.
If you would prefer, I could look into it myself and create a pull-request instead?
