vscode-test | Testing utility for VS Code extensions
kandi X-RAY | vscode-test Summary
kandi X-RAY | vscode-test Summary
Testing utility for VS Code extensions
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vscode-test
vscode-test Key Features
vscode-test Examples and Code Snippets
Community Discussions
Trending Discussions on vscode-test
QUESTION
I tried creating VS Code extension using the sample extension (yo code) provided in the documentation. I chose "typescript" as it's type of extension, while creating it. When I tried to run the extension, I get an error message .
...ANSWER
Answered 2021-Oct-04 at 13:29The error is due to the compilation not running or failing to run at the launch of the extension. Hence .js file not getting created on /out/* directory
- I solved the issue, by manually running tsc --watch from the root directory.
- I thought, the launch of the extension by default trigger the compilation, but that wasn't the case.
- The product documentation says,"press F5. This will compile and run the extension in a new Extension Development Host window." However, this isn't the case for me. Not sure, where it was actually failing .
- I've opened up an bug with Microsoft for this issue.
https://github.com/microsoft/vscode-extension-samples/issues/510
QUESTION
Right, so, the title isn't really any good. But basically the problem I have is that, while trying to make my own version of a plugin I use, I have been unable to run it.
What makes it stop working seems to be using a function imported from another local file (In typescript). I have tried everything I could think of, such as, copying a working extension and just replacing the code, changing the compiler settings copying the official extension example github. As well as changing the functions between async and not async.
I also tried running the original plugin from source to test if it was something with my environment. But that did work. Soooo... I have 0 clue about what could be the cause (Except for the imported functions).
(as I don't know what causes it I don't really know what parts would be helpful, so everything down below is of uncertain necessary level, I have also barely done anything with typescript or vscode extensions before)
The error message
...ANSWER
Answered 2021-Aug-18 at 21:38const fs = require("fs");
const readDir = promisify(fs.readdirectory);
QUESTION
I want to compile JSX files using '@babel/preset-react on VScode extension API. While doing this I faced an error just like below. I have tried a few ways to install but still can't get any results. It works on a basic node application but it doesn't work on VScode extension API.
...ANSWER
Answered 2021-Apr-30 at 20:42The biggest hint in that error is webpackEmptyContext. This isn't Node telling you that it failed to find @babel/preset-react" on the filesystem, it is Webpack telling you that it was unable to load @babel/preset-react" from it's bundle.
In the case of Babel, and anything with object-based config inputs, that is expected, because Webpack has no way to know that
QUESTION
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:52After 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.
QUESTION
I have created a simple VS Code extension which defines multiple tasks:
...ANSWER
Answered 2021-Apr-12 at 14:34A solution based on the example from github: microsoft/vscode-extension-samples.
This uses a more complete definition of vscode.TaskProvider. The important parts seem to be: interface CustomBuildTaskDefinition extends vscode.TaskDefinition and a complete taskDefinitions in package.json.
src/extension.ts
QUESTION
I made a vscode extension from the github template now to test i have to run this command according to the guide
...ANSWER
Answered 2021-Mar-23 at 13:22Use the current VSC by using an additional Launch config and write the index.(ts/js) file and your test files.
Select this config from the Run/Debug bar and press F5.
Now there is no need to download VSC.
QUESTION
I'm coding a vscode extension following the guide and I came accross an import problem in my server.ts file. Here is the file tree:
...ANSWER
Answered 2021-Mar-03 at 11:41The vscode package has been deprecated. It has now been split up into two packages which are @types/vscode and vscode-test. The reason for this refactoring can be found here.
You have included the @types/vscode dependency but not vscode-test.
Adding the vscode-test dependency should fix your issue i.e.
QUESTION
Have somebody an idea why my extension is not showing up in the sidebar ín Visual Studio Code? If I bring the extension in my extension folder, the extension works but do not show up in the sidebar.
Repo: https://github.com/peni4142/work-as-two
package.json:
...ANSWER
Answered 2020-Feb-03 at 19:54It looks like VSCode no longer shows extensions with an undefined publisher in the extensions list (this definitely used to work at some point). If I add "publisher": "test" to "package.json" it shows up:
It occurred to me to try this because of the undefined_publisher in the Log (Extension Host) output channel:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install vscode-test
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
