Cannot setup addons on neovim :'(

[Silzinc]

Hello! I am trying to setup a project with addons type definitions localised in ./addons from the project root. I first added lua-cjson-definitions with the following command:

git submodule add [email protected]:goldenstein64/lua-cjson-definitions.git addons/lua-cjson-definitions/

No problem here. I also put the following in my .luarc.json:

{
  "$schema": "https://raw.githubusercontent.com/sumneko/vscode-lua/master/setting/schema.json",
  "runtime": {
    "version": "Lua 5.1"
  },
  "workspace": {
    "checkThirdParty": true,
    "userThirdParty": ["./addons"]
  }
}

(I also tried putting an absolute path for the addons)
But when I start neovim on a file with local cjson = require("cjson"), no prompt for setting up the library, and no type checking... I tried with the following minimal config, without success:

vim.lsp.config["luals"] = {
	cmd = { "/path/to/lua-language-server" },
	root_markers = { { ".luarc.json", ".luarc.jsonc" }, ".git" },

	settings = {
		Lua = {
			runtime = {
				version = "LuaJIT",
			},
		},
	},
}

vim.lsp.enable("luals")

While the language server works, gives diagnostic, and seems to react to the other settings in the .luarc.json, I still cannot get my addon to work. Any ideas?

[corpserot]

Have you check out https://github.com/folke/lazydev.nvim? In any case, you can simply just ignore the addon stuff (primarily is a VSCode thing) and simply set the "workspace.library" in your project's .luarc.json (or LuaLS config):

{
    // your_addon/library/ contains all the *.lua definition files
    "workspace.library": ["path/to/your_addon/library"]
}

[Silzinc]

Yeah I use lazydev when developing neovim plugins or config. It's not adapted for general lua projects afaik, as it loads neovim plugins into the require path. Whenever you have a .luarc.json file in your project (required when not working on neovim plugins), lazydev notifies you that it's a bad idea to use both at the same time.

I tried putting each library in the "workspace.library" too, but it did not work either. However, emmylua had no issues so far (probably because they use some kind of heuristics to find addons too). I think I'll just use emmet for regular lua projects.