Module path resolution for js & mjs verticle factories fails on windows

[chefhoobajoob]

See reproducer here, using es4x 0.15.0: https://github.com/chefhoobajoob/es4x-graal-js-error-reproducer

For some reason, the mjs verticle factory is able to load the entry module if it has a .js file extension, but otherwise both factories are unable to resolve module paths when launching an es4x module or, if the module does get loaded and includes require or import statements, to resolve those paths.

[pmlopes]

the internal usage of URIs to refer to module paths seem to be incorrect on windows where slashes are mixed and drive leters miss a prefix extra /.

Running tests on windows seem to show for example:

file://N:\reactiverse\es4x\somefile.js

Where it should read:

file:///N:/reactiverse/es4x/somefile.js

[chefhoobajoob]

Is the code that's generating those file uri's with mixed slashes coming from graalvm, or are they under es4x/vertx control? new File(absolutePath).toURI() would probably do it

[pmlopes]

This was fixed on 0.16.0