add npm publish to server and client release process #71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry for the cheeky PR!
Thanks for the great tool!
A la #34, we would like to add RF LSP support for another client. We respect that a lot of servers will be built on the nodejs tooling, and go to great pains to support node-based language servers where possible (but are likewise trying to figure out how to bundle them for the browser, if possible).
It's somewhat unreasonable to expect end users to do git clone, add all the build/test dependencies. To avoid this, (at least) the server package would need to be accessible in a non-vscode places, which pretty much means npmjs (or I guess github, now, maybe).
Please consider publishing these!