Languages & Runtimes

The web languages are ready when you open a file. For almost everything else, there is an extension on Open VSX.

Built in, no extension required

TypeScript

IntelliSense, refactoring, and a choice of which TypeScript version the project uses.

JavaScript

Completions, @ts-check, and automatic type acquisition for npm libraries.

Node.js

Run and debug Node apps with tasks, the terminal, and the debugger.

JSON

Schema-aware completion and validation, including for package.json and tsconfig.json.

HTML

Tag completion, closing-tag sync, and path help for linked assets.

CSS, SCSS & Less

Property completion, color previews, and stylesheet validation.

Markdown

Live preview, path checks, and helpers for structured editing.

Emmet

Abbreviation expansion for HTML, CSS-family languages, and JSX/TSX.

PHP

Built-in basics, plus where to find richer language tools on Open VSX.

Everything else, via Open VSX

Python, Go, Rust, Java, C/C++, C#, PHP, Ruby, Swift, Kotlin, and the other languages people use day to day have language extensions on Open VSX. Those add IntelliSense, debugging, and refactoring in the same spirit as the built-in languages. Search for the language in the Extensions view. The first time you open a file Gyaanmitra does not fully support yet, it will usually suggest the extension to install.

Runtime and version management

Gyaanmitra does not manage language runtime versions itself. For Node.js, Python, and similar, keep using the version manager your project already uses (nvm, pyenv, and the like). They work in the integrated terminal because that terminal is a real shell. Once a runtime is on your PATH, or your shell profile activates it, Gyaanmitra's language tools pick it up.

Per-workspace interpreter/runtime selection

When a language has several versions installed, its extension usually adds its own interpreter command and a status bar item. Python virtual environments are the common case. Look for it after you install the language extension.