By looking at
settings-view you should be able to figure out which API call to uninstall a package.
Not really related, but I thought of a feature for atom packages depending on another package. For instance, whether it’s minimap plugins, autocomplete providers or build plugins in a build system, we’ll see more and more package whose purpose is to extend another package. These packages could just declare a
extend field in their
package.json with the name of the package they extend. Apm could prevent the installation of these packages if the master package is not installed, or even install it automatically. Also, uninstalling/deactivating the master package could do the same with all its plugins.
The settings view could regroup these packages as descendants of their master package (as an accordion in the left list). Settings of these packages could also be grouped in a single interface in the master settings view.