feat: replace wasm with node bindings

[branchvincent]

Hey, cool project!

This swaps the wasm bindings for native node bindings, fixing #17. Some things to note:

• tree-sitter-fish currently has broken node bindings, so we need the fix at fix node bindings ram02z/tree-sitter-fish#24
• The node parser doesn't have all the same methods (like equals, delete, fieldCount, nodeTypeCount) so I had to remove a few test cases from parser.test.ts
• I cleaned up some other deps, removing unused tsc (this was superseded by typescript), chai, tree-sitter-cli
• I dropped the preinstall script to allow installing with npm, which partially fixes Why is yarn required for the build? #48 and NPM Install Fail #57 (scripts/relink-locally.fish still requires yarn but I have some suggested packaging changes that I'll make in a separate PR to fully fix)
• Also added tests to CI, which exposed Tree.rootNode undefined in jest tests due to race condition tree-sitter/node-tree-sitter#181 causing flakey failures so added a suggested workaround

[ndonfris]

Hello! Awesome work here :)

My primary motivation for opening that discussion was because of the tree-sitter documentation which states:

Notice that executing .wasm files in node.js is considerably slower than running node.js bindings.

Unfortunately, upon further investigation, I did not find this to be case. Directly comparing these two dependencies locally, I found that the node bindings were significantly slower than the wasm bindings

wasm using web-tree-sitter	node using node-tree-sitter
720 fish files {functions,conf.d}/*.fish, config.fish	692 fish files functions/*.fish, config.fish
Elapsed time: 1.69s	Elapsed time: 3.53s
node version 22.12.0	node version 22.12.0

Please feel free to compare the startup timing yourself. Relevant change can be found here in the src/analyze.ts file.

note: that depending on your language client, and the value of set -gx fish_lsp_show_client_popups, the startup time might only be shown in your set -gx fish_lsp_logsfile /tmp/fish-lsp.logs file.

IMO, I think the performance difference is a little too large currently, and I'm not sure if it's worth the tradeoff as the web-tree-sitter and node-tree-sitter packages appear to be pretty noticeably inconsistent in what features they support. Indexing the completions/*.fish files is planned in v1.0.9, and that'd probably double the amount of files indexed, at least.

If we do plan on adopting the node bindings, I think it would be worth further documenting what differences there are between the two packages, and how to handle them in the future. The eventually 1.0.9 uses a lot of the SyntaxNode class, so switching to the node bindings will likely require a lot of changes to upstream branches (as seen on both PR #52 and the dirty branch fix/def-scope-extended, with the FishSymbol changes)

For now I'll leave this open, and continue looking into using the node bindings over wasm. Feel free to continue the discussion here, or on the old discussion. It's really unfortunate that the node bindings are so slow, as having features like typedocs and easier testing would be really nice to have.

---

On some of the other fixes you mentioned:

• I cleaned up some other deps, removing unused tsc (this was superseded by typescript), chai, tree-sitter-cli

• I dropped the preinstall script to allow installing with npm, which partially fixes Why is yarn required for the build? #48 and NPM Install Fail #57 (scripts/relink-locally.fish still requires yarn but I have some suggested packaging changes that I'll make in a separate PR to fully fix)

Please feel free to open a PR for this, I'd be happy to help you get it merged.

I've been meaning to finalize v1.0.8-3 for a while now, and I think this would be a great addition to that release. Here's my current plan for resolving the package manager issues.

Thanks again for such a thorough PR! Hoping we can merge it eventually.