go-language-server alternatives and similar packages
Based on the "Editor Plugins" category.
Alternatively, view go-language-server alternatives based on common mentions on social networks and blogs.
-
Go for Visual Studio Code
DISCONTINUED. An extension for VS Code which provides support for the Go language. -
GoSublime
A Golang plugin collection for SublimeText 3, providing code completion and other IDE-like features. -
coc-go language server extension for Vim/Neovim
Go language server extension using gopls for coc.nvim. -
Watch
Watches for changes in a directory tree and reruns a command in an acme win or just on the terminal. -
Local Golang playground
GNU/Emacs mode that setup local Go playground for code snippets like play.golang.org or even better :)
WorkOS - The modern identity platform for B2B SaaS
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of go-language-server or a related project?
README
A Go Language Server based on the Go Extension for Visual Studio Code
Wraps the VSCode Go extension from Microsoft into a language server, such that its functionality can be reused with other LSP-aware clients.
In the first iteration we will mock VSCode APIs or simulate their behavior backed by an LSP. We will maintain this as a fork of the original repository such that we can easily pick up incoming improvements of that by just rebasing. Once we got more confidence, we'd probably refactor the VSCode specific parts away.
[Original README.md](README_old.MD).
Mismatches and Challenges
- There is no such thing as the
activeTextEditor
in LSP. For services that have aTextDocumentItem
, we set it before calling the service impl, but for other services, e.g.executeCommand
we cannot make sure that they are performed on the correct document. - We have to use/mock/adapt a lot of global variables
Prerequisites
Make sure the go
command is available from your path and that the GOPATH
environment variable points to where your go packages are installed. Some go
packages are necessary:
go get -u -v github.com/nsf/gocode
go get -u -v github.com/uudashr/gopkgs/cmd/gopkgs
go get -u -v github.com/ramya-rao-a/go-outline
go get -u -v github.com/acroca/go-symbols
go get -u -v golang.org/x/tools/cmd/guru
go get -u -v golang.org/x/tools/cmd/gorename
go get -u -v github.com/fatih/gomodifytags
go get -u -v github.com/haya14busa/goplay/cmd/goplay
go get -u -v github.com/josharian/impl
go get -u -v github.com/tylerb/gotype-live
go get -u -v github.com/rogpeppe/godef
go get -u -v golang.org/x/tools/cmd/godoc
go get -u -v github.com/zmb3/gogetdoc
go get -u -v golang.org/x/tools/cmd/goimports
go get -u -v sourcegraph.com/sqs/goreturns
go get -u -v github.com/golang/lint/golint
go get -u -v github.com/cweill/gotests/...
go get -u -v github.com/alecthomas/gometalinter
go get -u -v honnef.co/go/tools/...
go get -u -v github.com/sourcegraph/go-langserver
go get -u -v github.com/derekparker/delve/cmd/dlv
go get -u -v github.com/davidrjenni/reftools/cmd/fillstruc
Note: this list comes from here.
Build and usage
- Run
npm install
to install the package dependencies. - Run
npm run compile
to compile the Typescript to Javascript. - Run the server with
node ./out/src-vscode-mock/cli.js --stdio
.