VSCode-Extensions | A-to-Z List of Useful JavaScript VSCode Extensions

by yogain123 JavaScript Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | VSCode-Extensions Summary

VSCode-Extensions is a JavaScript library typically used in Plugin, Visual Studio Code applications. VSCode-Extensions has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A-to-Z List of Useful JavaScript VSCode Extensions

Support

Quality

Security

License

Reuse

Support

VSCode-Extensions has a low active ecosystem.

It has 12 star(s) with 3 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

VSCode-Extensions has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of VSCode-Extensions is current.

Quality

VSCode-Extensions has 0 bugs and 0 code smells.

Security

VSCode-Extensions has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

VSCode-Extensions code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

VSCode-Extensions is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

VSCode-Extensions releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of VSCode-Extensions

Get all kandi verified functions for this library.

VSCode-Extensions Key Features

No Key Features are available at this moment for VSCode-Extensions.

VSCode-Extensions Examples and Code Snippets

No Code Snippets are available at this moment for VSCode-Extensions.

Community Discussions

Trending Discussions on VSCode-Extensions

Module compiled against a different NODE_MODULE_VERSION when developing an extension for vscode

QUESTION

Module compiled against a different NODE_MODULE_VERSION when developing an extension for vscode

Asked 2022-Mar-23 at 22:45

I'm trying to use node's tree-sitter package in my vscode extension, but I get the following error:

Activating extension 'extension name' failed: The module '.../node_modules/tree-sitter/build/Release/tree_sitter_runtime_binding.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 93. This version of Node.js requires NODE_MODULE_VERSION 89. Please try re-compiling or re-installing the module (for instance, using npm rebuild or npm install)..

From what I understand, the NODE_MODULE_VERSION is the version of node's ABI. However, I couldn't even find a release of node that has NODE_MODULE_VERSION 89 in the official website.

What I've tried:

Deleting the node_modules folder and reinstalling the packages.
Running npm rebuild tree-sitter --update-binary from the top directory.
Rebuilding the tree-sitter package with node-gyp rebuild and node-gyp rebuild --target=(my node version) from the node_modules/tree-sitter directory.
Switching node versions using nvm.

None of that helped. I understand from here that changing node versions won't help, as I confirmed when I tried

console.log(process.version); // v14.16.0

console.log(process.versions.modules); // 89

This gave the same output no matter which node version I used. I also tried rebuilding the tree-sitter package using that node version node-gyp rebuild --target=14.16.0, but I get the same error, however this time it says the module was compiled using NODE_MODULE_VERSION 83, which is consistent with what node's site says.

How do I resolve this error? Any help is appreciated.

...

ANSWER

Answered 2022-Mar-23 at 22:45

As I suspected, the version of node ABI used by vscode extensions is the ABI version used by vscode's internal electron. According to this source

Native Node.js modules are supported by Electron, but since Electron has a different application binary interface (ABI) from a given Node.js binary (due to differences such as using Chromium's BoringSSL instead of OpenSSL), the native modules you use will need to be recompiled for Electron...

This explains why I couldn't find NODE_MODULE_VERSION 89 in node's site.

Next, I checked what version of electron my build of vscode uses. To do this, I simply checked the package.json that came with vscode (/usr/lib/code/package.json on linux, I guess that it is inside the folder vscode is installed on on windows).

Next, following the instructions from electron's site, rebuild the module using the package electron-rebuild. To specify a target version, simply run

./node_modules/.bin/electron-rebuild -v [version]

However, I have no source for this but it seems that tree-sitter does not currently support newer versions of electron, so the build fails. This seems to be because of a change in V8's API (according to this).

The author linked his solution here. I copied his changes and the build succeeded.

Note that I had to replace the existing node addon with the newly built one.

Source https://stackoverflow.com/questions/71527006

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install VSCode-Extensions

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: