Allow easy download on CI servers about edge-launcher

[auchenberg]

I have released v1.2.2 and published the new version to NPM.

Please be ware that the binary now is located in /dist/x86/

[dotnetCarpenter]

@nickmccurdy I finally found out that the real issue is that I was using appveyor which has Windows Server 2012 as the default VM which doesn't have Edge. I'm hoping that we will get access to Windows Server 2016 and the issue will go away.

I would still prefer to use a newer version than 1.0.0.0, like 1.2.0.0. But unless someone fork this project and publish it to npm...

[nickserv]

Fantastic, thank you! I'll update karma-edge-launcher soon.

[nickserv]

Have you gotten the npm package to work outside of karma-edge-launcher? I'm wondering if we can isolate the issue to this package, otherwise it would be a bug in karma-edge-launcher.

[dotnetCarpenter]

@nickmccurdy I haven't tried the npm package, but spotted your issue #20. I will give the npm package a shot. If it works, do you mind forking this project and release an updated npm package with another name?

[nickserv]

Yeah, I created #20 when I noticed the npm package was out of date. The reason I didn't fix it myself is that the npm package's source is not available, and if I'm understanding this correctly it means I wouldn't be able to make a package with the same metadata. I'll double check this though.

Worst case, it probably would be a good idea to temporarily fork this to get up to date npm packages until it's fixed upstream. If it's okay with the package maintainers, I can help publish the new versions to the existing packages. My npm username is nicolasmccurdy. I would need the package.json and any other artifacts (if I remember correctly it's just the exe which is on GitHub Releases anyway, so maybe that's it).