Normalize paths for builds on windows

[paulvarache]

Transforms backslashes to forward slashes to fix builds on windows

[coveralls]

Coverage decreased (-0.1%) to 98.701% when pulling 5f93f57 on paulvarache:win-build into 34e2605 on Tonejs:dev.

[tambien]

thanks for the PR! i wonder if using path.posix is a more elegant approach here. Feels a little weird to be inspecting the platform and node provides a cross-platform way to generate unix-style paths.

does collect_tests.js also needs the same update to work on Windows? it does a similar thing as collect_deps.js

[paulvarache]

I updated the PR to fix the tests on windows. The npm script is using the $npm_config_dir and $npm_config_file variables but this is not resolved on windows. I added a normalizeVariable method that deal with that, but could also use process.env to have a unified API across platform, but I'm not sure if the args file and dir of collect_tests.js are used anywhere else and don't want to break things.

I would be happy to use the file/dir arguments and merge them with $npm_config_dir and $npm_config_file env variables in the script. Updating the npm script collect:tests to not take any file or dir args from the unix shell. Something like this:

const file = args.file || process.env.npm_config_file;
const dir = args.dir || process.env.npm_config_dir;

As for the path resolution, I looked into posix, but it won't convert Windows style path into posix style paths, it is just two different implementations of the path module (see nodejs/node#12298).

[adenflorian]

@tambien
@paulvarache 's solution works for me (windows 10, node v10.14.1), but your commit 8070135 doesn't. There are a couple open issues on path.posix for windows:

• path.posix.resolve, path.posix.relative return wrong path on Windows nodejs/node#13887
• path.posix.relative returns different results for *nix and Windows versions of node nodejs/node#13683

When using posix, for me, it's outputting things like this into index.js when building:
require("./../../C:/Users/Me/Tone.js/Tone/component/Follower");

Think we could go with paul's solution for now?