Description
The current tree-sitter-svelte parser used across the ecosystem appears to be effectively unmaintained. It is an important infrastructure for syntax highlighting and language tooling in editors and LSPs like Neovim and Zed. The parser has not seen a commit to master in around two years, several pull requests have been left open for months, I don't think there is interest in adding maintainers for the repository.
Zed is using an off-main commit hash in its official extension to work around these issues but we should not expect them to keep it up to date, effort has been made to keep it up to date but I don't expect Zed team to switch to another grammar that might get unmaintained with time.
Because of this, the Svelte ecosystem is in a fragile position: an important piece of editor tooling depends on a parser that does not appear to have active ownership or reliable maintenance. Other projects, such as Ripple, already maintain their own tree-sitter implementation.
Proposed solution
It would be nice for the Svelte ecosystem if the team was to officially host or maintain a tree-sitter parser repository.
If the core Svelte team does not want to maintain it directly, I think it wouldn't be a big problem to find some voluunteers to keep it up to date, most of the work is already done.
Alternatives
No response
Additional Information, eg. Screenshots
No response
Description
The current tree-sitter-svelte parser used across the ecosystem appears to be effectively unmaintained. It is an important infrastructure for syntax highlighting and language tooling in editors and LSPs like Neovim and Zed. The parser has not seen a commit to master in around two years, several pull requests have been left open for months, I don't think there is interest in adding maintainers for the repository.
Zed is using an off-main commit hash in its official extension to work around these issues but we should not expect them to keep it up to date, effort has been made to keep it up to date but I don't expect Zed team to switch to another grammar that might get unmaintained with time.
Because of this, the Svelte ecosystem is in a fragile position: an important piece of editor tooling depends on a parser that does not appear to have active ownership or reliable maintenance. Other projects, such as Ripple, already maintain their own tree-sitter implementation.
Proposed solution
It would be nice for the Svelte ecosystem if the team was to officially host or maintain a tree-sitter parser repository.
If the core Svelte team does not want to maintain it directly, I think it wouldn't be a big problem to find some voluunteers to keep it up to date, most of the work is already done.
Alternatives
No response
Additional Information, eg. Screenshots
No response