Fixes babel-register for Windows paths

[rozele]

Babel was not compiling anything from react-packager/src when run from Windows, including the recently added node-haste stuff, which has been causing problems for some people. This change fixes that.

Fixes #10033
Fixes #8899

[facebook-github-bot]

By analyzing the blame information on this pull request, we identified @janicduplessis and @sam-swarr to be potential reviewers.

[rozele]

babel-core (used by babel-register) takes a dependency on slash, which only "normalizes" paths (with '/') if they consist of only ASCII characters. So, babel-register breaks down for any React Native users on Windows when their project paths contain non-ASCII characters.

[rozele]

This would be redundant if babel/babel#4631 gets accepted.

[rozele]

We may want to consider merging this, as I don't know when or if the change to babel will be accepted.

[rozele]

The babel PR is accepted, so once the next version of babel is released, we can close out this PR and instead upgrade babel.

[facebook-github-bot]

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @davidaurelio as a potential reviewer. Could you take a look please or cc someone with more context?

[hramos]

@rozele do you still plan to ship this?

[hramos]

cli.js conflict needs to be addressed.

[rozele]

Thanks for checking @hramos. Since my PR to babel was accepted, and someone recently upgraded babel (680df89), this PR is no longer relevant.