Open vasily-kirichenko opened 7 years ago
looks like it's an atom-languageclient issue
It's not Windows specific - atom-languageclient had not yet been published because it was still in developer preview.
In order to unblock a few people I have gone ahead and published it for now as 0.1.1. You'll need to bump your package.json.
I'd recommend using specific versions for now as we'll probably break a few times before 1.0.0 as things stabilize and then after that we'll adopt a semver (if I do that now we'd probably end up on 5.x.y before launch)
I updated the package to use the version of atom-languageclient from NPM
atom-languageclient has been published since then - you should be able to just specify the version you want (I'd specify an exact version number for now until we hit 1.0.0 in case we break stuff)