@akaroml Not sure why do you need to Uninstall listener here. Actually when an extension depends on another extension, you can add it as a dependency in extensionDependencies section of package.json. Dependent extension should not bother about the depending extensions existence or not. It should be other way round. We also make sure if an extension is uninstalled, we do not uninstall it if there is an extension depending on it.

It looks to me that in your case B depends on A and A wants to do some clean up when B is uninstalled. This is showing some cyclic dependencies.

@aeschli FYI

This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.

I have a different use case but the same request for an uninstall life-cycle hook/event. I have an extension that needs to clean up some dirs/files it creates on the OS when uninstalling but should leave alone if simply deactivating (closing a vscode instance).

Makes sense

Related #14444

Now you can provide node script (javascript) to run after the extension is uninstalled, using the property vscode:uninstall under the scripts property in package.json.

Example

"scripts": {
    "vscode:prepublish": "tsc -p ./",
    "vscode:uninstall": "node ./out/src/extensionUninstall"
},

Using this hook, you can clean up the stuff that your extension has created.

@sandy081 "Using this hook, you can clean up the stuff that your extension has created." I can't clean up vs code user settings on that hook. In my case, i add some settings. It says that it can not find 'vscode' module when that hook runs. Should i go the user.settings path and modify with plain node js?

@GabrielBB Yes, this hook does not provide you access to vscode api. Please create a new feature request for that.