feat: expose configs

1 files changed, 0 insertions, 45 deletions

diff --git a/lua/lspconfig/rescriptls.lua b/lua/lspconfig/rescriptls.lua
deleted file mode 100644
index 13ea1b73..00000000
--- a/lua/lspconfig/rescriptls.lua
+++ /dev/null
@@ -1,45 +0,0 @@
-local lspconfig = require 'lspconfig'
-local configs = require 'lspconfig/configs'
-
-local name = 'rescriptls'
-
-configs[name] = {
-  default_config = {
-    cmd = {},
-    filetypes = { 'rescript' },
-    root_dir = lspconfig.util.root_pattern('bsconfig.json', '.git'),
-    settings = {},
-  },
-  docs = {
-    description = [[
-https://github.com/rescript-lang/rescript-vscode
-
-ReScript language server
-
-**By default, rescriptls doesn't have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path.
-You have to install the language server manually.
-
-You can use the bundled language server inside the [vim-rescript](https://github.com/rescript-lang/vim-rescript) repo.
-
-Clone the vim-rescript repo and point `cmd` to `server.js` inside `server/out` directory:
-
-```lua
-cmd = {'node', '<path_to_repo>/server/out/server.js', '--stdio'}
-
-```
-
-If you have vim-rescript installed you can also use that installation. for example if you're using packer.nvim you can set cmd to something like this:
-
-```lua
-cmd = {
-  'node',
-  '/home/username/.local/share/nvim/site/pack/packer/start/vim-rescript/server/out/server.js',
-  '--stdio'
-}
-```
-
-Another option is to use vscode extension [release](https://github.com/rescript-lang/rescript-vscode/releases).
-Take a look at [here](https://github.com/rescript-lang/rescript-vscode#use-with-other-editors) for instructions.
-]],
-  },
-}