Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Split the language server in its own npm module

See original GitHub issue

Ciao!

I got the language server working in VIM! Very fun! I didn’t push anything in my repo gianarb/vim-coc yet because I didn’t figure out how to release it yet.

Let me explain my point here to see if you can help me. One of the plugins available in VIM to speak with an LSP is vim-coc that embeds the vscode language server client in VIM. It means that I had to create a bridge similar to this one, in order to make vim smart enough to start and talk with your Grammarly LSP. It works just fine.

import {ExtensionContext, services, workspace, LanguageClient, TransportKind} from 'coc.nvim'

export async function activate(context: ExtensionContext): Promise<void> {
  const serverOptions = {
    module: "/Users/gianarb/git/grammarly/out/server.js",
    transport: TransportKind.ipc,
    options: {
      cwd: workspace.root,
    }
  }
  const clientOptions = {
    documentSelector: ['markdown', 'md'],
  }
  const client = new LanguageClient(
    'coc-grammarly', // the id
    'coc-grammarly', // the name of the language server
    serverOptions,
    clientOptions
  )
  context.subscriptions.push(services.registLanguageClient(client))
}

Obviously /Users/gianarb/git/grammarly/out/server.js is a problem. Other projects like the css-language-server developed by Microsoft don’t have the extension and the LS in the same project, and it is easier for other editors to re-use it. My hope is that having the Grammarly-lsp as a standalone project with only the dependencies it needs will make it easier to reuse.

https://github.com/microsoft/vscode-css-languageservice

Does it sound reasonable to you? 😃 Thanks