The module 'l\node_modules\tree-sitter\build\Release\tree_sitter_runtime_binding.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 115. This version of Node.js requires NODE_MODULE_VERSION 118. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`)

[suraiya-syed]

The module 'l\node_modules\tree-sitter\build\Release\tree_sitter_runtime_binding.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 115. This version of Node.js requires NODE_MODULE_VERSION 118. Please try re-compiling or re-installing the module (for instance, using `npm rebuild` or `npm install`)

[verhovsky]

your npm run rebuild command needs to match the Electron version of your VS Code. Open VS Code, press in the top left About Visual Studio Code, copy the "Electron: 27.2.3" (or whatever) string then change the rebuild command in package.json to

    "rebuild": "electron-rebuild --version 27.2.3"

[gaspardruan]

I have the same problem when importing tree-sitter in a simple electron template, then I rebuild successfully as above said.
But the app can't start owing to the error:

[9776:0223/013812.099:ERROR:node_bindings.cc(154)] Fatal error in V8: v8_ArrayBuffer_NewBackingStore When the V8 Sandbox is enabled, ArrayBuffer backing stores must be allocated inside the sandbox address space. Please use an appropriate ArrayBuffer::Allocator to allocate these buffers, or disable the sandbox.
[9776:0223/013812.099:ERROR:crashpad_client_win.cc(863)] not connected

I found the description about the problem in electron document:

How will I know if my app is impacted by this change?
Attempting to wrap external memory with an ArrayBuffer will crash at runtime in Electron 20+.
If you don't use any native Node modules in your app, you're safe—there's no way to trigger this crash from pure JS. This change only affects native Node modules which allocate memory outside of the V8 heap (e.g. using malloc or new) and then wrap the external memory with an ArrayBuffer. This is a fairly rare use case, but some modules do use this technique, and such modules will need to be refactored in order to be compatible with Electron 20+.

I also read the #177 , but is seems that the problem still occurs.