use nvim-lspconfig

Author: antonk52

README.md

@@ -24,33 +24,29 @@ See if your editor supports language servers or if there is a plugin to add supp
 
 ### Neovim
 
-Example uses [`nvim-lspconfig`](https://github.com/neovim/lspconfig)
+Example uses [`nvim-lspconfig`](https://github.com/neovim/nvim-lspconfig)
 
 ```lua
-local configs = require'lspconfig/configs'
-
-if not configs.cssmodules then
-    configs.cssmodules = {
-        default_config = {
-            cmd = {'cssmodules-language-server'},
-            filetypes = {'javascript', 'javascriptreact', 'typescript', 'typescriptreact'},
-            init_options = {
-                camelCase = 'dashes',
-            },
-            root_dir = require('lspconfig.util').root_pattern('package.json')
-        },
-        docs = {
-            description = 'TODO description',
-            default_config = {
-                root_dir = '[[root_pattern("package.json")]]'
-            }
-        }
-    }
-end
-
-configs.cssmodules.setup {}
--- or
--- configs.cssmodules.setup {on_attach = custom_on_attach}
+require'lspconfig'.cssmodules_ls.setup {
+    -- provide your on_attach to bind keymappings
+    on_attach = custom_on_attach,
+    -- optionally
+    init_options = {
+        camelCase = 'dashes',
+    },
+}
+```
+
+**Known issue**: if you have multiple LSP that provide hover and go-to-definition support, there can be races(example typescript and cssmodules-language-server work simultaneously). As a workaround you can disable **definition** in favor of **implementation** to avoid conflicting with typescript's go-to-definition.
+
+```lua
+require'lspconfig'.cssmodules_ls.setup {
+    on_attach = function (client)
+        -- avoid accepting `go-to-definition` responses from this LSP
+        client.resolved_capabilities.goto_definition = false
+        custom_on_attach(client)
+    end,
+}
 ```
 
 ### [coc.nvim](https://github.com/neoclide/coc.nvim)