The extension is very heavyweight startup, 2s on my machine and a lot of cpu cycles each time even if I'm not using it.
Ideally your activation events would be the existing onCommand events, and a workspaceContains even that looks for the typical azurite cache files indicating azurite is in use in the workspace.
At worst, change * to onStartupFinished so that vscode startup time is not impacted by the extension loading.
Due to this behavior I generally have to disable it and only enable it in workspaces I use it, it would be nice for it to be more behaved.
The extension is very heavyweight startup, 2s on my machine and a lot of cpu cycles each time even if I'm not using it.
Ideally your activation events would be the existing onCommand events, and a
workspaceContains
even that looks for the typical azurite cache files indicating azurite is in use in the workspace.At worst, change
*
toonStartupFinished
so that vscode startup time is not impacted by the extension loading.Due to this behavior I generally have to disable it and only enable it in workspaces I use it, it would be nice for it to be more behaved.