vscode-extension | Zeplin for Visual Studio Code

 by   zeplin TypeScript Version: Current License: MIT

kandi X-RAY | vscode-extension Summary

kandi X-RAY | vscode-extension Summary

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

Zeplin for Visual Studio Code lets you quickly access the designs you’re working on, follow design changes, open the Jira issues they’re attached to —all from within VS Code. .
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              vscode-extension has a low active ecosystem.
              It has 32 star(s) with 3 fork(s). There are 11 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              There are 5 open issues and 13 have been closed. On average issues are closed in 38 days. There are 6 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of vscode-extension is current.

            kandi-Quality Quality

              vscode-extension has 0 bugs and 0 code smells.

            kandi-Security Security

              vscode-extension has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              vscode-extension code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              vscode-extension is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              vscode-extension releases are not available. You will need to build from source code and install.
              Installation instructions are available. Examples and code snippets are not available.

            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-extension
            Get all kandi verified functions for this library.

            vscode-extension Key Features

            No Key Features are available at this moment for vscode-extension.

            vscode-extension Examples and Code Snippets

            No Code Snippets are available at this moment for vscode-extension.

            Community Discussions

            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

            QUESTION

            Disable competing language servers / code highlighters
            Asked 2022-Mar-22 at 09:29

            I want to add a language server to handle completion / highlighting / etc. for a file. As a basis for testing stuff I am using an example from Microsoft (https://github.com/microsoft/vscode-extension-samples/tree/main/lsp-sample) and changed it to be active for any File. This language server highlights any word in all capital letters.

            When opening a C++ File, I get the highlighting / completion of my language server and the default one for C++ (See image).

            I would like to detect if some other extension / build in highlighter is active for a file and deactivate it for this workspace or the current file if it is impossible for the current workspace)

            1. Is there a way to do this in a generic way where I do not have to know which extensions are highlighting code?
            2. If no, is there a way to do this, if I know a set of extensions I want to deactivate?
            ...

            ANSWER

            Answered 2022-Mar-22 at 09:29

            I finally had enough time to try around a bit more and found that providing your own language for the same extension is enough.

            In package.json I added an element in contributes.languages with extensions containing .cpp (since I am using cpp files for testing).

            I also copied over some implementation code from an example.

            This suppressed the default highlighter and code completion for cpp files. Since i am only implementing a semantic token provider, I can see the default highlighting before my provider takes over. (I think this could be solved by adding a syntax highlighter, but this is already sufficient fo my preliminary testing)

            I am not sure, how stable all of this would be as a plugin (I only tested in Extension Development Host mode)

            Here an image of the results:

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

            QUESTION

            vscode: Using the proposed API cannot find "https://raw.githubusercontent.com/microsoft/vscode/master/src/vs/vscode.proposed.d.ts"
            Asked 2021-Dec-03 at 20:25

            I'm trying to use registerInlineCompletionItemProvider proposed API. I'm following the instructions in https://code.visualstudio.com/updates/v1_58 and here https://github.com/microsoft/vscode-extension-samples/tree/main/inline-completions. Both of them ask to copy https://raw.githubusercontent.com/microsoft/vscode/master/src/vs/vscode.proposed.d.ts to your local directory, but that file doesn't exist. Also when I follow the instructions to install the extension I always get an error because it doesn't exist:

            ...

            ANSWER

            Answered 2021-Nov-24 at 22:21

            You need https://github.com/microsoft/vscode/blob/main/src/vscode-dts/vscode.proposed.inlineCompletions.d.ts.

            The file was split up 13 days ago in a4d426a, tracked in #131165.

            Apparently not all docs have been updated.

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

            QUESTION

            VS Code extension with webpack and link to node_modules
            Asked 2021-Nov-22 at 16:49

            I created a VS Code extension which uses a Webview. In the Webview I have a link to a file in the node_modules folder which I added to the html as recommended by various sources (e.g. vscode-codicons-sample):

            ...

            ANSWER

            Answered 2021-Nov-22 at 16:49

            I decided to go with @MikeLischke's suggestion and copy the required files into the dist folder, which is packaged. But I didn't want to do it manually, so I did the following.

            NodeModulesAccessor

            Firstly, I created a class which does the mapping between the files in the node_modules folder and the destination in the packaged dist folder.

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

            QUESTION

            (neo)vim/emacs support of source decorations (meta source code info)?
            Asked 2021-Aug-03 at 15:55

            This is a dump non-vim, non-emacs user question to the users of those editors.

            VScode supports such things as decorations of the code:

            • color highlight the text ranges
            • or insert some helper text content that actually does not belong to the source content but is visible for the user.

            https://github.com/microsoft/vscode-extension-samples/blob/main/decorator-sample/README.md

            Do 1) vim, 2) neovim, 3) emacs support this kind of editor extension?

            ...

            ANSWER

            Answered 2021-Aug-03 at 15:55

            Yes, all three support something to that effect.

            For vim, a way to do something similar to the example is to use the :syntax command.

            To approximate the example (small numbers one color, big numbers another), you could say:

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

            QUESTION

            How to use VSCode's formatter from the command line?
            Asked 2021-Jul-06 at 20:28

            Someone in my team uses vim, but the rest of us use VSCode's default formatter (i.e. vscode.typescript-language-features). I'd like to add a git precommit hook or something that invokes the formatter without opening up the app.

            See also:

            ...

            ANSWER

            Answered 2021-Jun-23 at 20:33

            There is a great git hooks tool called Husky and its documentation can be found here.

            Here is an example of it inside of a package.json file that uses pretty-quick to execute prettier whenever a git pre-commit is executed.

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

            QUESTION

            I'm not entirely sure how to use QuickInput in VS-Code
            Asked 2021-Jun-22 at 23:19

            i recently asked a question "how do i add custom parameters to a custom command in a custom vs code extension" and realized through some of the comments that you cant enter parameters in the command palette. so i looked for alternate options. one i came across was quickInput which allows the user to enter text into a window. however, being new to typescript, along with having documentation for more knowledgeable users on my hands, i couldn't figure out how to use it. please help!

            update: since "quickInput" couldn't be found, i decided to opt for "showInputBox" but wasn't sure how to use the "title" parameter. but just for testing porpuses i decided to test the following:

            ...

            ANSWER

            Answered 2021-Jun-22 at 23:19

            Some sample code I have used before (modified):

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

            QUESTION

            How do I use icons on a TreeItem in a VSCode extension when using webpack
            Asked 2021-Jun-03 at 11:18

            I have troubles adding icons to a TreeItem in my VSCode extension. When I load the extension, the item has a blank space where the icon ought to be.

            I have tried to mimic the nodeDependency example. I have the following in extension.ts:

            ...

            ANSWER

            Answered 2021-Jun-03 at 11:18

            Webpack changes __filename, so your attempt to go to the resource directory fails.

            Add the following to webpack.config.js to leave __filename unchanged:

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

            QUESTION

            add icon to activity bar in visual studio code extension
            Asked 2021-May-09 at 20:45

            I am new to VSC extension development.

            I started with the extension hello world and I want to add an icon to the activity bar and get a notification when it is clicked.

            I add these lines to package.json

            ...

            ANSWER

            Answered 2021-May-09 at 20:45

            You must also specify a "views" item that matches the id of your viewContainer

            Try adding the following right after the "viewsContainers" object in the "contributes" section of package.json

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

            QUESTION

            VSCode Extension: get a files old and new versions
            Asked 2021-Apr-28 at 11:52

            I am trying to develop a VSCode extension which requires the current open file and same file from previous git revision/commit. Which is same as clicking the open changes button in vs code.

            I Tried using SCM and QuickDiffProvider as shown in this sample-extension, but its giving "unable to resolve resource" when trying to open the old file in vscode.

            snippet from extension.ts

            ...

            ANSWER

            Answered 2021-Apr-28 at 11:52

            After struggling so much to find alternative solution to get the diff of file, I found that we can use vscode.editors, to access all the open editors.

            Example: In git diff we will have 2 editors (left: old and right: new), so we can use the following code to access old and new content.

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

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

            Vulnerabilities

            No vulnerabilities reported

            Install vscode-extension

            Install Zeplin from Visual Studio Code extension marketplace.
            Open the new Zeplin sidebar.
            Login to Zeplin.

            Support

            See CONTRIBUTING.md for details.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/zeplin/vscode-extension.git

          • CLI

            gh repo clone zeplin/vscode-extension

          • sshUrl

            git@github.com:zeplin/vscode-extension.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular TypeScript Libraries

            developer-roadmap

            by kamranahmedse

            vscode

            by microsoft

            angular

            by angular

            TypeScript

            by microsoft

            ant-design

            by ant-design

            Try Top Libraries by zeplin

            storybook-zeplin

            by zeplinTypeScript

            zeplin-html-to-pdf

            by zeplinJavaScript

            zem

            by zeplinJavaScript

            react-native-extension

            by zeplinJavaScript