With regard to disabling extensions, it is not necessary to do this most of the time. Extensions are conditionally loaded based on their Activation Events.
For example, if you open a Python project, you would not expect a JavaScript-related extension such as Vetur to be loaded. An author could choose to load the extension always of course, but you hope they don't! You can read this article for a more in-depth discussion on this - VS Code Performance – How to Optimize Visual Studio Code and Choose the "Best" Extensions.
You can check which extensions have been loaded in the extensions sidebar. If an extension was loaded, you will see a loading time next to its name. You can see in the screenshot below that the extensions, ESLint and Format Code Action, have been loaded for my project. By clicking on the extension, you also see this in the "Runtime Status" tab also.
You can check an extension's Activation Events in the "Feature Contributions" tab.
If you do find yourself, repeating customization like KR mentioned across projects, you can create a custom set-up for a language or project type - see Customise VS Code for a project, or per language .
With regard to disabling extensions, it is not necessary to do this most of the time. Extensions are conditionally loaded based on their
Activation Events.For example, if you open a Python project, you would not expect a JavaScript-related extension such as Vetur to be loaded. An author could choose to load the extension always of course, but you hope they don't! You can read this article for a more in-depth discussion on this - VS Code Performance – How to Optimize Visual Studio Code and Choose the "Best" Extensions.
You can check which extensions have been loaded in the extensions sidebar. If an extension was loaded, you will see a loading time next to its name. You can see in the screenshot below that the extensions, ESLint and Format Code Action, have been loaded for my project. By clicking on the extension, you also see this in the "Runtime Status" tab also.
You can check an extension's Activation Events in the "Feature Contributions" tab.
If you do find yourself, repeating customization like KR mentioned across projects, you can create a custom set-up for a language or project type - see Customise VS Code for a project, or per language .
Wow, that's a whole lot information
I really appreciate your hard work, Thanks. Keep on writing these cool stuff!!🔥🔥
Thanks KR. 😀
Great info Rob , thanks!