Supported extensions
List of extensions that can be automatically configured to use tools from
mise.
If you want to configure it manually, search for
Mise: Configure extension sdk path... in the command palette.
- By default, the extensions are automatically configured to use
mise shims. You can disable this feature in the settings. - If you want to share your
.vscode/settings.jsonfile with others, you can enableconfigureExtensionsUseSymLinks. This will create a folder in your.vscodedirectory with a symlink to the tools installed bymise. - If you want to disable the automatic configuration of extensions, see the set-up guide.
| Extension | Settings | Comment |
|---|---|---|
| Python | python.defaultInterpreterPath | You will still need to select the interpreter. See this discussion |
| Go | go.goroot, go.alternateTools | |
| Java | jdk.jdkhome | |
| Shellcheck | shellcheck.executablePath | |
| NodeJS | debug.javascript.defaultRuntimeExecutable.pwa-node | |
| Deno | deno.path | |
| Bun | bun.runtime | |
| Ruff | ruff.path | |
| php, php built-in | php.validate.executablePath, php.debug.executablePath | Does not work with symlinks |
| julia | julia.executablePath | Does not work with shims |
| erlang | erlang.erlangPath | Does not work with shims |
| dart | dart.sdkPath | Does not work with shims or symlinks |
| flutter | dart.flutterSdkPath | Does not work with shims or symlinks |
| zig | zig.path, zig.zls.path (install zls with mise) | Does not work with shims or symlinks |
| sops | sops.binPath | |
| ginkgo test explorer | ginkgotestexplorer.ginkgoPath | |
| buf | buf.commandLine.path | |
| biome | biome.lsp.bin | Not enabled by default. Update "mise.configureExtensionsAutomaticallyIgnoreList" to [] to enable it. Use it only if you don’t install biome with npm. |
Extensions which have built-in support for mise:
- Ruby, with ruby-lsp
- Elixir
will look for
miseand install the lsp server automatically
Extensions that are not supported:
- Rust does not offer to update the cargo path automatically. See this discussion for workarounds.
If you would like to add one, you can open a PR that updates src/utils/supportedExtensions.ts