Extensions

Extensions & Open VSX

Extensions install from Open VSX. Search for a language, a theme, or a tool, and add it from inside the editor.

Why Open VSX

Gyaanmitra uses the same extension API the wider editor ecosystem already writes for. Language tools, themes, linters, and small helpers are available through Open VSX, a marketplace run as an Eclipse Foundation project. There is no separate Gyaanmitra package format.

Same extension API

An extension written for that API works here as it is. You do not learn a Gyaanmitra-only package format.

One public marketplace

Open VSX is a public catalog, and its terms allow any product to use it. Install the extension you want.

Installing extensions

1

Open the Extensions view

Click the Extensions icon in the Activity Bar, or press Ctrl+Shift+X.

2

Search

Type a language, framework, or tool name. Results come live from Open VSX.

3

Install

Click Install. Most extensions start right away. Some ask you to reload the window first.

4

Manage installed extensions

The same view lists everything you have installed. You can disable one for this workspace or everywhere, update it, or uninstall it.

Installing a VSIX file directly

If an extension is not on Open VSX yet, install its .vsix file with Extensions: Install from VSIX… in the Command Palette. That is also how you add an extension that only your team uses.

Recommended extensions per project

A workspace can suggest extensions to anyone who opens it. List them in .vscode/extensions.json. That helps a team share the same linter or formatter without asking each new person to install it by hand.

.vscode/extensions.json

{
  "recommendations": [
    "esbenp.prettier-vscode",
    "dbaeumer.vscode-eslint"
  ]
}

Extension settings sync

Turn on Settings Sync (from the Accounts icon in the Activity Bar) to keep your extensions, settings, keybindings, and snippets in step across every machine you use Gyaanmitra on. You do not reinstall them each time.

Disabling extensions for troubleshooting

If Gyaanmitra is acting strangely, try Help → Start Extension Bug Bisect, or Disable All Installed Extensions. That option is available at launch, or for one session from the … menu in the Extensions view. It is the quickest way to see whether an extension is the cause.

Extension authors

Writing an extension, or moving one over? See Extension authoring notes for webview CSP, asWebviewUri, workspaceFolders, and Node.js navigator notes.