| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
| |
Co-authored-by: Delice0 <59118341+Delice0@users.noreply.github.com>
|
| |
|
| |
Fixes the issue by changing "enabled" to "enable"
|
| |
|
|
|
| |
When flow is not in global PATH, try node_modules/.bin/flow relative
to the project root before falling back to npx. This covers the common
case where flow-bin is a local devDependency.
|
| | |
|
| | |
|
| |
|
|
| |
rzls.nvim is deprecated and the support of razor is now moved into roslyn.nvim
with the author for rzls.nvim joining to maintain roslyn.nvim
|
| | |
|
| |
|
| |
avoid spawning extra LSP instances by fixing the reuse_client logic.
|
| |
|
|
|
|
| |
shuck is a lightning fast shell linter and language server written in Rust.
It supports bash, zsh, posix, and mksh dialects.
https://github.com/ewhauser/shuck
|
| |
|
|
|
|
|
|
| |
Problem:
oxfmt and oxlint have the ability to use vite plus config, as mentioned here:
https://github.com/voidzero-dev/vite-plus/issues/629
Solution:
update the configs to reflect that.
|
| |
|
|
|
|
|
| |
Problem:
Only matching `action.yml`
Solution:
Match `action.yaml` also.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Problem:
`emmylua_ls` is emerging as the preferred Lua LS for Neovim, but the
config provided by nvim-lspconfig is almost useless.
Solution:
Update the config to provide hints similar to that of `lua_ls`.
|
| | |
|
| |
|
|
|
| |
1. `plugin/lspconfig.lua`: LspRestart timer was never closed after firing, leaking a libuv handle on every invocation.
2. `lsp/muon.lua`: Formatting cmd (a list) with %s, producing table: 0x... instead of the command.
|
| |
|
|
|
|
|
|
| |
Panache is a language server (formatter, and linter) for Markdown,
Quarto, and R Markdown. It's built in Rust and uses a lossless CST
parser. It supports integrating external formatters and linters. It's
packaged at crates.io, NPM, PyPi, and as a VSIX extension at VS Code
Marketplace and Open VSX. Binaries are provided directly from the GitHub
repo.
|
| |
|
|
| |
per https://github.com/Kotlin/kotlin-lsp/commit/75ddb7586e0170ed93912b0be5d67e0a45769ee6
, the new name of the launcher is `intellij-server`, not `kotlin-lsp`.
|
| |
|
|
|
|
| |
Esbonio v2 can no longer be started with the top-level esbonio command.
Switch to 'esbonio.server' which is compatible with v1 and v2.
See: https://github.com/swyddfa/esbonio/pull/1098
|
| | |
|
| | |
|
| | |
|
| |
|
| |
The repo moved from elixir-lang to expert-lsp (https://github.com/expert-lsp/expert)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
`before_init` (#4390)
|
| | |
|
| |
|
|
|
|
|
|
| |
Problem:
'gd' and 'gdscript3' are file extentions, not filetypes (as per the
result of running `getcompletion('', 'filetype')` command in neovim
Solution:
Remove them, leaving only 'gdscript'
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The next release of `buf` will include LSP features that include support
for buf config files. This follows the approach that other LSPs follow
for specifying custom filetypes (a comment + adding that custom
filetype to filetypes).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
`find_tailwind_global_css` attempted to address #4204, where `experimental.configFile` was set using the return value of `vim.fs.find()`.
The language server rejected this with `Invalid experimental.configFile
configuration, not initializing` because `configFile` expects either a string or
a key-value record (object), not an array/list. This was a syntax issue, not
a detection issue.
Using the correct syntax for `configFile` in Lua should be
sufficient to address the original issue. Right now, `find_tailwind_global_css`
always runs for users who haven't explicitly set `configFile` — overriding the
LSP's native detection and **forcing anyone who wants to opt out to manually set
all entry-points by hand.**
Solution:
- Remove `find_tailwind_global_css` entirely and restores `configFile` to its
default `nil` so the `tailwindcss` LSP handles project detection natively.
- Simplify `before_init` based on [this suggestion from the initial
PR](https://github.com/neovim/nvim-lspconfig/pull/4222#discussion_r3018499628).
The following syntax worked for me while testing to explicitly set the
`configFile` based on the [official
docs](https://github.com/tailwindlabs/tailwindcss-intellisense#tailwindcssexperimentalconfigfile)
for single entry-point:
> [!NOTE]
> Single entry-point is resolved relative to the workspace root (`root_dir` — verify with `:checkhealth vim.lsp`)
```lua
vim.lsp.config('tailwindcss', {
settings = {
tailwindCSS = {
experimental = {
-- v3: config file
configFile = 'tailwind.config.js',
-- v4: CSS entry-point
-- configFile = 'src/styles/app.css',
},
},
},
})
```
For projects with multiple entry-points, or different projects, the following
syntax can be used for multiple entry-points:
> [!NOTE]
> Keys are relative to `root_dir` as above, but from my testing on macOS, absolute paths worked better
```lua
vim.lsp.config('tailwindcss', {
settings = {
tailwindCSS = {
experimental = {
configFile = {
['tailwind.config.js'] = '/Users/username/path/to/project-a/**',
['src/main.css'] = '/Users/username/path/to/project-b/**',
},
},
},
},
})
```
#### Project or Local Configuration
For project-specific settings without modifying your global Neovim config:
1. Enable in your Neovim config:
```lua
vim.o.exrc = true
```
2. Create `.nvim.lua` in the project root:
```lua
vim.lsp.config('tailwindcss', {
settings = {
tailwindCSS = {
experimental = {
configFile = 'tailwind.config.ts',
},
},
},
})
```
3. Open `.nvim.lua` and run `:trust` to allow the file, then restart Neovim.
4. Verify with `:checkhealth vim.lsp`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
stylelint now has an official LS:
[@stylelint/language-server](https://github.com/stylelint/vscode-stylelint/tree/main/packages/language-server)
|
| |
|
|
|
|
|
| |
Problem: no LSP config exists for vimdoc (vim help) files.
Solution: add config for `vimdoc-language-server`, a language server
providing formatting, diagnostics, document symbols, and go-to-definition
for vimdoc files.
|
| |
|
|
|
|
|
|
| |
The current biome project root logic uses JS package manager
lockfiles to get the project root in mono repos.
If one is not using any JS (wasm) and raw CSS, that doesn't work out.
In those cases, only a biome.json exists as a marker on where the
frontend's project root inside the mono repo may be located.
|
