We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since fc2144b the fallback file watcher using chokidar no longer works.
Can reproduce in neovim using this config:
in ~/.config/nvim/after/ftplugin/svelte.lua
~/.config/nvim/after/ftplugin/svelte.lua
vim.lsp.start({ name = "svelte", cmd = { "/path/to/language-tools/packages/language-server/bin/server.js", "--stdio" }, root_dir = vim.fs.root(0, { "package.json" }), capabilities = { workspace = { didChangeWatchedFiles = false, }, }, })
With this, changes in TypeScript files aren't detected in Svelte files.
Changes in TypeScript files should be detected in Svelte files. For example, diagnostics should update.
svelte-language-server
Reverting fc2144b fixes this issue, but I'm not sure how to fix it while keeping chokidar v4.
The text was updated successfully, but these errors were encountered:
fix: migrate glob file watch for chokidar v4 (#2551)
7c23767
#2539 chokidar v4 removes all glob support. This migrates fallback watcher and CSS global var to use the ignored config
No branches or pull requests
Describe the bug
Since fc2144b the fallback file watcher using chokidar no longer works.
Reproduction
Can reproduce in neovim using this config:
in
~/.config/nvim/after/ftplugin/svelte.lua
With this, changes in TypeScript files aren't detected in Svelte files.
Expected behaviour
Changes in TypeScript files should be detected in Svelte files. For example, diagnostics should update.
System Info
Which package is the issue about?
svelte-language-server
Additional Information, eg. Screenshots
Reverting fc2144b fixes this issue, but I'm not sure how to fix it while keeping chokidar v4.
The text was updated successfully, but these errors were encountered: