Node module version mismatch when integrating tree-sitter with VS Code extension

[StachuDotNet]

Node module version mismatch when integrating tree-sitter with VS Code extension

[StachuDotNet]

I've since had some success, in abandoning the tree-sitter npm package in favor of the web-tree-sitter npm package, building my parser to .wasm and using that instead.

[sogaiu]

IIUC, if the performance is not an issue, going the .wasm route has the advantage of not having to build for multiple architectures.

I understand that this is a route that seems to have worked out for some cases for VSCode extensions.

[rtllxndr]

There are few steps required to do what you want.
First, you need to rebuild it for electron, it will fix NODE_MODULE_VERSION message.
I used @electron/rebuild and set some environment variables from docs.
Second, after that you would face another message, related to memory sandbox, which is enabled in electron (and vscode).
Check this pr #177 to solve this issue.
And to fix No rule to make target 'Release/obj.target/tree_sitter/vendor/tree-sitter/lib/src/lib.o', needed by 'Release/obj.target/tree_sitter.a' you probably need to download submodule, like this git submodule update --init --recursive