Automatically Enable Extensions Based on Project Files

[Majoramari]

It would be helpful if VS Code could automatically enable or disable extensions based on project structure instead of requiring manual management for every workspace.

Currently, I can use workspace settings to enable extensions per project, but I have to do this manually for every new project. This becomes tedious when working across multiple languages or frameworks. For example, I don’t need rust-analyzer or golang.go running all the time only when I open a project that requires them.

Allow extensions to be automatically enabled based on certain conditions, such as:

• If a specific file exists in the root (e.g., go.mod, Cargo.toml, package.json).
• If the project matches a certain type (e.g., a Next.js or SvelteKit project).

Example configuration:

{
  "extensions.autoEnable": {
    "rust-analyzer": { "exists": ["Cargo.toml"] },
    "golang.go": { "exists": ["go.mod"] },
    "svelte-vscode": { "exists": [".svelte-kit"] }
  }
}

Benefits:

• Avoids unnecessary extensions running in unrelated projects.
• Reduces manual setup when creating new projects.
• Improves startup time by not loading unused extensions.

This would streamline workflows and improve performance, especially for developers who work across multiple technologies.

Basically like Lazyvim in Neovim

[iwangbowen]

Have you tried Profiles in Visual Studio Code

[Majoramari]

Have you tried Profiles in Visual Studio Code

I tried workspaces too, but I still see the mention solution is hassle-free because it's not manual.