Vscode: Extensions startup loading order

[muuvmuuv]

There has been an issue here without a potential solution: #13292

I don't want to give extensions the power to set their priority of loading in my VSCode I rather want myself setting a priority to some extensions I want to have loaded before the others.

For example, I have an extension that shows me saved projects (Project Manager) and I want this to be loaded at first to fast select a project before the rest is loaded because when I have selected a project the viewport will be reloaded anyway.

My solution, having a option like this:

"workbench.extensions.loadingOrder": {
    "alefragnani.project-manager": {
      "priority": 10000
    }
  },

all other extensions would be loaded as before after these prioritised extensions.

[beaksandclaws]

This feature would be amazing. My use case is the exact same - I'd love the ability to set Project Manager as the first extension loaded, so I can get to work right away while other extensions are still processing.

[Jn58]

I need same feature with different reason. I'm using vim extension and whenever I run vscode, I have to wait until vim extension being loaded before I start editing. It's quite annoying.

[Taoquitok]

Commenting on this for the same reason as others, Being able to bump Project Manager to load ahead of other extensions would be a lovely way of getting to pick a project quicker.
Even with disabling most extensions within the default load, there's enough of a slow down ahead of seeing project manager load to make me sigh each time.

[alefragnani]

I‘ll take a look if there is something that can be changed to make VS Code _prioritize_ the extension.

I didn’t look at VS Code source code yet, but maybe the excess of activationEvents may be moving it to the end. Maybe the _kind_ of activationEvents. Maybe _alphabetic_ reasons 😆

Let’s see what I can find.

[ashkitten]

my issue is slightly different - i use direnv's nix integration to import project-specific dependencies into the shell environment when i cd into the project dir. however, even though i can create an extension to load the direnv environment in vscode, other extensions such as rls-vscode may still load before the environment is loaded, causing them to not work since the binary is not in the path yet. simply put, i need a way to delay the startup of other extensions until mine is loaded.

[LosEagle]

My use case would be to be able to specify which extensions take precedence over others when multiple extensions change same features.

For instance if I install IntelliJ keybinds and Vim, IntelliJ keybinds will override some of Vim's hotkeys and I'd prefer it to be the other way around so that Vim overrides the keybinds extension hotkeys.

[Rizary]

@ashkitten did you manage to solved your use case? I've been looking for the solution and come to this thread. And by looking at your comment, I have same case when I want to load direnv extension before other extensions.

[ashkitten]

no. i haven't been able to use vscode for my workflow because of this issue so i just use neovim still. bit of a shame.

[anka-213]

@Rizary I've been using the extension nix environment selector with some success. It does however force you to reload VS code whenever the environment changes.

[Rizary]

@Rizary I've been using the extension nix environment selector with some success. It does however force you to reload VS code whenever the environment changes.

I'm using flake and I've try that extension without success. I'm in WSL2 too, and using rust-analyzer. I've tried with Haskell-language-server extension, it works after several retry. So maybe rust-analyzer didn't do retry as haskell-language server did