nvim-lspconfig - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	docs: add deprecation notice to lua/lspconfig/configs #4189	Justin M. Keyes	2025-11-15	1	-0/+7
\|
*	fix(tailwindcss): improved tailwindcss detection (#3648)	Maksim Terpilovskii	2025-03-20	1	-5/+5
\| \| \| \| \| \| \| \| \| \| \| \| \|	Problem: The Tailwind CSS language server is enabled for any workspace containing a `.git` folder, a `node_modules` folder, or a `package.json` file, which is not ideal. Solution: Introduce a specific check for the `tailwindcss` package within `package.json` file using `insert_package_json` method from `util` (this approach is used in `eslint` config). Since the latest version of Tailwind CSS (v4) no longer requires `postcss.config.` and `tailwind.config.` files, these can no longer be relied upon as sole criteria for enabling Tailwind CSS LSP.
*	refactor: deprecate util.find_git_ancestor	dundargoc	2024-12-14	1	-1/+1
\| \| \| \|	Work on https://github.com/neovim/nvim-lspconfig/issues/2079.
*	fix(regression): fix for vim.fs.find regression not returning parent ↵	Jacob Reed	2024-12-13	1	-4/+3
\| \| \| \|	directory (#3505)
*	refactor: deprecate util.find_package_json_ancestor	dundargoc	2024-12-13	1	-1/+1
\| \| \| \|	Work on https://github.com/neovim/nvim-lspconfig/issues/2079.
*	refactor: deprecate util.find_node_modules_ancestor	dundargoc	2024-12-08	1	-3/+4
\| \| \| \|	Work on https://github.com/neovim/nvim-lspconfig/issues/2079.
*	refactor(docs): drop redundant default_config #3398	Justin M. Keyes	2024-10-24	1	-3/+0
\| \| \| \| \| \| \|	Problem: default_config duplicated in `docs` items. Solution: delete it. docgen autogenerates this now.
*	refactor: rename "server_configurations" => "configs" #3330	Justin M. Keyes	2024-10-01	1	-0/+130
	Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.