-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to use the latest version of this LSP from NPM? #1075
Comments
Hi! You're right, the release process to npm broke at some point. @fhammerschmidt do you have any ideas here, as to why the packages no longer are published to npm? |
Might be just that the NPM token is expired? It's already 2 years old. |
Created and set a new token, let's see. |
Yeah, works again! |
@fdaciuk can we close this then? |
I think so @zth! But the latest version on NPM is still 1.58.0 🤔 I also saw that the |
Hm, yes it should be. Looks like we'll need to investigate more then. |
I think this was finally sorted, and I released a |
@snatvb please open a separate issue with that, it looks unrelated to this particular issue. |
@fdaciuk the latest master was successfully published on npm: https://www.npmjs.com/package/@rescript/language-server/v/1.63.0-next-1e935ad.0 As for the tag I have a possible fix here: #1078 |
It worked, thanks guys 😍 |
That worked too @fhammerschmidt, but I need to pass the exact version instead of just "rescriptls@latest-master". But it is working, thanks 😍 |
does |
Not with the tag. Mason only works with versions so I have to use |
But it is not a big problem to be honest @fhammerschmidt. You can close this issue if you want, the LSP is now usable again :D |
I'm using Neovim with Mason, but the most recent version I can install is v1.58.0:
I can see that the last build failed to publish the package to NPM.
Is there anything I can do to help fix this?
The text was updated successfully, but these errors were encountered: