New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible eslint related race condition #1730
Comments
do you get this issue with vscode? I doubt if this is related to nvchad, also related to microsoft/vscode-eslint#1229 |
backup your nvchad config and try this init.lua as your config https://github.com/nvim-lua/kickstart.nvim ( no need to setup lsp in it, just install eslint binary from Mason window) , lemme know if this works, if yes then its an issue with nvchad 🤔 |
@rauchg Totally unrelated, but if you're anything like me and forgot about the null-ls |
@rauchg you should try passing the vim.lsp.buf.format { bufnr = bufnr, async = false } |
closing this as it doesnt seem to be a nvchad issue |
I frequently get post-save errors that complain that ESLint can't access a file. It seems completely random. If I save again it usually succeeds.
My
~/.config/nvim/lua/custom/plugins/lspconfig.lua
:My
~/.config/nvim/lua/custom/plugins/null-ls.lua
:I've installed both
eslint-lsp
andeslint_d
via:Mason
My environment details:
The text was updated successfully, but these errors were encountered: