Monokle extension code preview

Based on boilerplate content.

What's in the folder

This folder contains all of the files necessary for your extension.
package.json - this is the manifest file in which you declare your extension and command.
src/extension.ts - this is the main file and the execution entry point of the extension.
- The file exports one function, activate, which is called the very first time your extension is activated.

Get up and running straight away

Press F5 to open a new window with your extension loaded.
Run your command from the command palette by pressing (Ctrl+Shift+P or Cmd+Shift+P on Mac).
Set breakpoints in your code inside src/extension.ts to debug your extension.
Find output from your extension in the debug console.

Make changes

You can relaunch the extension from the debug toolbar after changing code in src/extension.ts.
You can also reload (Ctrl+R or Cmd+R on Mac) the VS Code window with your extension to load your changes.

Explore the API

You can open the full set of our API when you open the file node_modules/@types/vscode/index.d.ts.

Run tests

Open the debug viewlet (Ctrl+Shift+D or Cmd+Shift+D on Mac) and from the launch configuration dropdown pick Extension 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/test/suite/extension.test.ts or create new test files inside the test/suite folder.

Go further

Follow UX guidelines to create extensions that seamlessly integrate with VS Code's native interface and patterns.
Reduce the extension size and improve the startup time by bundling your extension.
Publish your extension on the VS Code extension marketplace.
Automate builds by setting up Continuous Integration.