mirror of
https://github.com/eclipse-theia/theia.git
synced 2025-12-04 04:24:13 -05:00
Page:
Testing VS Code Extensions
Pages
2024
Cleaning Local Storage
Code Improvement Areas
Code Organization
Coding Guidelines
Consuming Builtin and External VS Code Extensions
Dev Meetings 2018
Dev Meetings 2019
Dev Meetings 2020
Dev Meetings 2021
Dev Meetings 2022
Dev Meetings 2023
Dev Meetings 2024
Dev Meetings
Eclipse Theia Roadmap
Eclipse Theia Twitter Strategy
Eclipse Theia contributors: Intellectual Property (IP) guide
FAQ
Home
Internationalization Updates
LSP and Monaco Integration
Registering CQs
Technical Meeting
Testing VS Code Extensions
Theia Community Call
Theia Developer Conference 2019
Theia Plugin Implementation
Theia Re Licensing
No results
4
Testing VS Code Extensions
Moritz Eysholdt edited this page 2019-07-31 20:42:52 +02:00
How to test:
-
create
pluginsfolder under Theia repo folder -
Google for an extension (*.vsix file) and download it to the
pluginsfolder:1 -
check that the extension is installed,
Viewmain menu ->Plugins -
test functionality of the extension
Alternatively, if you want to try any of the existing vscode-extension-samples without packaging them into a .vsix with vsce. You can do the following:
- Clone the samples:
git clone https://github.com/microsoft/vscode-extension-samples.git
- Build one of the samples, for instance
webview-sample:
cd vscode-extension-samples/webview-sample/ && npm i && npm run compile
- Make sure the
outfolder exists with theextension.jscontent. - Start Theia and open a workspace on the sample. In this case, it is
path/to/the/vscode-extension-samples/webview-sample/. - F1 >
Hosted Plugin: Start Instance. Your instance will open in a new window on port3030. - Try the extension.
- For instance, with the
webview-sample, F1 >Cat Coding: Start cat coding session> 🐈
- For instance, with the
If something does not work:
- file an issue
- please check first that there is no similar issue already
- mention which extension
- what does not work
- always check your expectations with what VS Code does
- check browser console and server logs for errors and warnings. If there are some, mention them in the issue as well
1Alternatively, you can use the command "Deploy plugin by id" from the command palette. When asked for a parameter, enter the following: vscode:extension/<exension id>. "<extension id>" stands for the "Unique Identifier" from the extension homepage in the VS Code Marketplace.
Project Management
- Roadmap
- Dev Meetings
- Technical Meetings
- Community Call
- Intellectual Property (IP) guide
- Registering CQs (Deprecated)
Documentation