- This folder contains all of the files necessary for your web extension.
package.json
* this is the manifest file in which you declare your extension and command.src/web/extension.ts
* this is the main file for the browserwebpack.config.js
* the webpack config file for the web main
- install the recommended extensions (amodio.tsl-problem-matcher, ms-vscode.extension-test-runner, and dbaeumer.vscode-eslint)
- Run
npm install
. - Place breakpoints in
src/web/extension.ts
. - Debug via F5 (Run Web Extension).
- Execute extension code via
F1 > Hello world
.
- You can relaunch the extension from the debug toolbar after changing code in
src/web/extension.ts
. - You can also reload (
Ctrl+R
orCmd+R
on Mac) the VS Code window with your extension to load your changes.
- You can open the full set of our API when you open the file
node_modules/@types/vscode/index.d.ts
.
- Open the debug viewlet (
Ctrl+Shift+D
orCmd+Shift+D
on Mac) and from the launch configuration dropdown pickExtension Tests
. - Press
F5
to run the tests in a new window with your extension loaded. - See the output of the test result in the debug console.
- Make changes to
src/web/test/suite/extension.test.ts
or create new test files inside thetest/suite
folder.- The provided test runner will only consider files matching the name pattern
**.test.ts
. - You can create folders inside the
test
folder to structure your tests any way you want.
- The provided test runner will only consider files matching the name pattern
- Follow UX guidelines to create extensions that seamlessly integrate with VS Code's native interface and patterns.
- Check out the Web Extension Guide.
- Publish your extension on the VS Code extension marketplace.
- Automate builds by setting up Continuous Integration.