You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
vscode.extensions Doesn't Update On Installing / Removing / Disabling Extensions without restarting #14444
I need to configure my extension code-settings-sync with the feature that when a user installs the extension and doesn't restart the vs code and neither enable the extension, I need to make the sync backup for that extension when installed.
Installation Process : when installed and not restarted.
Expected Behaviour: vscode.extensions.all should show the newly installed extension with enabled false flag
So I can get that extension and make a sync.
Current Behaviour
It doesn't appear in vscode.extensions.all until I restart the code by clicking the enable button or other way.
Uninstall Process: when uninstalled and not restarted.
Expected Behaviour: vscode.extensions.all should not show that extension or some flag like removed true
So I can get that extension remove from user's list and make a sync excluding that extension.
Current Behaviour
It doesn't remove from vscode.extensions.all until i restart the code
This is the scenario for installing/ uninstalling.
Same goes for disabling and enabling the extension I need to know which extensions are disabled or enabled.
Reacted by Michael Klement, Christhopher Lion, Matteo Gazzoni, Alexandre Le Foll, Fredrik Averpil, tamasfoldi, Aurelio De Rosa, Raul Santos, carlo-salinari, Márk Sági-Kazár and 926 more
Reacted by ahdung, fullstack, Paul Leverett, Yousef Shanawany, a2k and Escape0707
Reacted by Jonathan, William Cantin, Anton Matosov, Taylor Dolezal, Shawn Chow, Titus Woo, Benjamin Tavosloi, Raqib Abdullah, edwinabt, Gerson Goulart and 39 more
Reacted by Cody Swartz, Omar Tan, Atanas Georgiev Sqnkov, Victor Moura Cortez, Quang Ln, Andrew Klassen, George Pantazis, Hiroaki SHIBUKI, Dawson Botsford, EvanWang and 38 more
Reacted by Rainer Martinez, Serhat Teker and Martín Cigorraga
changed the title [-]Newly Installed Extensions (not enabled and restarted) doesnt appear in vscode.extensions[/-][+]Installing / Removing Extensions (not enabled and restarted) doesnt update in vscode.extensions[/+]on Oct 25, 2016
Shan Khan (@shanalikhan) I would like to what is the need to have an extension that is disabled... I am trying to understand the functionality/feature that requires this.
When you see my extension the main idea behind is to sync all the user installed extensions and settings file sync across multiple platforms.
When user install one extension and save the settings when it opens the code in office it does download the latest extensions and settings.
Initially user were able to sync these things manually to server and download then manually, now my aim is to make this process automatic so when user change any settings it upload all the settings file and the extensions to the server and download the settings and extensions when code is opened in other computer or office.
For now, the automatic process is working fine with the settings as when the settings change it automatic upload the settings and other data files in the server but for extension i am facing issue when the extension is download it doenst initialte the upload process as that object doenst contains all the extension that were downloaded untul the code is restarted so it would be better to add the downloaded extension in the list of extensions in the code but with a flag that shows its not enabled yet waiting for restart so i can save the settings.
Hope you know all the process now :)
Reacted by Nonoroazoro, xiaodeaux and Martín Cigorraga
Why do you need to sync the settings for a newly installed extension given that extension is not enabled or running. Settings of such extensions are not available they are active. It means user cannot modify settings of them.
So, I am thinking what is the use case of Syncing such settings which are not active and not modified?
i think Installing the extension should be seperate from the scenario of enabled or not.
Also when user install the extension i havent seen any property to disable the extension.
Also when user installs the extension on next restart the it will be enabled already so why not updating the object even on installing with a flag its disabled or enable ,as its already updating on restarting.
This is for my scenario for now, if it adds in the object many other doors to code for other extension would open
Shan Khan (@shanalikhan) Sorry, I still do not understand that what is the issue / what functionality is missing when you get the settings after restart?
Is it that you are trying to sync / export installed extensions information ?
I think it is not a good idea just to open the doors for everybody without a proper use case.
Anything can be applied by some extension A that has funtionality when user downloads any extension B , A should performed some task.
A proper use case should define the task.. not some task :)
So your issue is that if user installs an extension and does some export / sync using your extension (without restart), you do not have information about the installed extension and same with uninstalled extension ?
alexandrudima Here is a scenario where extension writers need more extension info (enabled / disabled) to export user preferences like installed extensions and others
I think the underlying desire here (and Shan Khan (@shanalikhan) correct me if I'm wrong) is to synchronize Visual Studio Code's state across machines. If that is the case, then there are a lot more (some even more basic) things to consider:
theme
installed extensions (also the disabled ones)
selected extension enable/disable options
view state (what files are in the working set, where is the cursor position inside them)
all other things we store in mementos (there are a lot more, such as last string searched, etc etc)
Regarding the disabled extensions, I think the problem is that Shan Khan (@shanalikhan) 's code might think that the extension got uninstalled meanwhile it is only temporarily disabled. We can think about listing disabled extensions in vscode.extensions.all, but then we'd need to prohibit calling activate() on such disabled extensions.
Reacted by Michael Klement, Gertjan Reynaert, Shan Khan, Darren Schroeder, Christhopher Lion, iamwrm, Matteo Gazzoni, Raul Santos, Austin Matherne, AlexZhao and 31 more
Reacted by Matteo Nicoletti, AbdulSamii Ajala, Shan Khan, Escape0707, Martín Cigorraga and Thorbjørn Horgen
alright, it would be great if you can raise this issue in your next meetings with the teams and let us know about the updates when would be possible to implement this.
Reacted by Ryan Altvater, Abdul Rauf, Carl Meyertons, Edvards Lazdāns, Escape0707, Axetroy, Juan Leni, Martín Cigorraga, Simon Siefke, Jeff Lewis and 1 more
Reacted by Martín Cigorraga, Jesse Jackson, Darryl, Thorbjørn Horgen and kanlukasz
More than two years after opening this issue, a minimum of at least 1000 user want this feature and all we do is waiting? Is there anything we can do to speed things up? It's a bit annoying how useful extensions trying to help automate things are blocked by such a minimal extension API..
Reacted by Agostino Carandente, KyleDavidE, Pradyun Gedam and Thorbjørn Horgen
What I understand is needed is an API that exposes all the installed extensions and enablement state per workspace, that also differentiates between built-in and external ones.
This is specially true when one works with different projects involving different technology stacks -- what makes enabling and disabling extensions per workspace a bless.
This, I think, is a behavior a lot of us are looking for VSC to have.
Right now, every time I set up a new project, I have to spend again a good amount of time to manually replicate the configuration on the other (two) machines.
My experience with VS Code so far is not pleasant at all. First, I have tried to install the 'Live Server' extension from the list of extensions, but there seems to be no extensions at all in my VS Code editor. Is there something I am missing please
We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.
Shan Khan (@shanalikhan) Hi
I have a similar issue to yours. Did the team come up with any solution for determining the number of disabled extensions through an API? I posted the issue but I was referred to this one.
Activity
[-]Newly Installed Extensions (not enabled and restarted) doesnt appear in vscode.extensions[/-][+]Installing / Removing Extensions (not enabled and restarted) doesnt update in vscode.extensions[/+]sandy081 commentedon Oct 27, 2016
Shan Khan (@shanalikhan) I would like to what is the need to have an extension that is disabled... I am trying to understand the functionality/feature that requires this.
Thanks
shanalikhan commentedon Oct 27, 2016
Sandeep Somavarapu (@sandy081)
When you see my extension the main idea behind is to sync all the user installed extensions and settings file sync across multiple platforms.
When user install one extension and save the settings when it opens the code in office it does download the latest extensions and settings.
Initially user were able to sync these things manually to server and download then manually, now my aim is to make this process automatic so when user change any settings it upload all the settings file and the extensions to the server and download the settings and extensions when code is opened in other computer or office.
For now, the automatic process is working fine with the settings as when the settings change it automatic upload the settings and other data files in the server but for extension i am facing issue when the extension is download it doenst initialte the upload process as that object doenst contains all the extension that were downloaded untul the code is restarted so it would be better to add the downloaded extension in the list of extensions in the code but with a flag that shows its not enabled yet waiting for restart so i can save the settings.
Hope you know all the process now :)
sandy081 commentedon Oct 27, 2016
Why do you need to sync the settings for a newly installed extension given that extension is not enabled or running. Settings of such extensions are not available they are active. It means user cannot modify settings of them.
So, I am thinking what is the use case of Syncing such settings which are not active and not modified?
shanalikhan commentedon Oct 27, 2016
i think Installing the extension should be seperate from the scenario of enabled or not.
Also when user install the extension i havent seen any property to disable the extension.
Also when user installs the extension on next restart the it will be enabled already so why not updating the object even on installing with a flag its disabled or enable ,as its already updating on restarting.
This is for my scenario for now, if it adds in the object many other doors to code for other extension would open
sandy081 commentedon Oct 27, 2016
Shan Khan (@shanalikhan) Sorry, I still do not understand that what is the issue / what functionality is missing when you get the settings after restart?
Is it that you are trying to sync / export installed extensions information ?
I think it is not a good idea just to open the doors for everybody without a proper use case.
shanalikhan commentedon Oct 27, 2016
Anything can be applied by some extension A that has funtionality when user downloads any extension B , A should performed some task.
Yes, instantly on when the extension is downloaded.
sandy081 commentedon Oct 27, 2016
So your issue is that if user installs an extension and does some export / sync using your extension (without restart), you do not have information about the installed extension and same with uninstalled extension ?
sandy081 commentedon Oct 27, 2016
alexandrudima Here is a scenario where extension writers need more extension info (enabled / disabled) to export user preferences like installed extensions and others
alexdima commentedon Oct 27, 2016
I think the underlying desire here (and Shan Khan (@shanalikhan) correct me if I'm wrong) is to synchronize Visual Studio Code's state across machines. If that is the case, then there are a lot more (some even more basic) things to consider:
Regarding the disabled extensions, I think the problem is that Shan Khan (@shanalikhan) 's code might think that the extension got uninstalled meanwhile it is only temporarily disabled. We can think about listing disabled extensions in
vscode.extensions.all, but then we'd need to prohibit callingactivate()on such disabled extensions.Shan Khan (@shanalikhan) Am I close to understanding your scenario?
shanalikhan commentedon Oct 27, 2016
Yes, Thanks
Look forward for it.
There is already another issue opened for API support for Themes and file icons:
#12178
and Disabling Extensions with API :
#15466
May be one single feature can cover then all in upcoming build so Code Settings Sync extension will start working with its full features
34 remaining items
sandy081 commentedon Aug 31, 2018
What I meant is to validate your features list and consolidate them in the description. It will be easy to get lost if not in description.
shanalikhan commentedon Aug 31, 2018
alright, it would be great if you can raise this issue in your next meetings with the teams and let us know about the updates when would be possible to implement this.
shanalikhan commentedon Oct 12, 2018
GuskiS commentedon Nov 5, 2018
Are there any news on this?
Gerschtli commentedon Dec 3, 2018
More than two years after opening this issue, a minimum of at least 1000 user want this feature and all we do is waiting? Is there anything we can do to speed things up? It's a bit annoying how useful extensions trying to help automate things are blocked by such a minimal extension API..
pradyunsg commentedon Feb 9, 2019
https://code.visualstudio.com/updates/v1_31#_no-reload-on-install
There's definitely work happening on this.
sandy081 commentedon Feb 11, 2019
Shan Khan (@shanalikhan) With 1.31 release we expose
extensions.onDidChangewhen extensions change, like when an extension is installed/uninstalled/enabled/disabled/But an extension is added or removed only if it supports no reload.
Let me know if this is good enough, if not, please update the additional requirements on top of it?
cig0 commentedon Apr 30, 2019
Hi Sandeep Somavarapu (@sandy081),
What I understand is needed is an API that exposes all the installed extensions and enablement state per workspace, that also differentiates between built-in and external ones.
This is specially true when one works with different projects involving different technology stacks -- what makes enabling and disabling extensions per workspace a bless.
This, I think, is a behavior a lot of us are looking for VSC to have.
Right now, every time I set up a new project, I have to spend again a good amount of time to manually replicate the configuration on the other (two) machines.
Thanks!
steshie-cmd commentedon Jul 29, 2020
My experience with VS Code so far is not pleasant at all. First, I have tried to install the 'Live Server' extension from the list of extensions, but there seems to be no extensions at all in my VS Code editor. Is there something I am missing please

steshie-cmd commentedon Jul 29, 2020
Secondly, I have tried to type in the basic command of '$ whoami' in the command line but the editor is not returning any results at all

vscode-triage-bot commentedon Nov 5, 2020
We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding and happy coding!
sandy081 commentedon Nov 5, 2020
We support Settings Sync feature inside VS Code as a core feature now - #2743
anasir975 commentedon Aug 4, 2022
Shan Khan (@shanalikhan) Hi
I have a similar issue to yours. Did the team come up with any solution for determining the number of disabled extensions through an API? I posted the issue but I was referred to this one.