Skip to main content
Use uninstall to remove managed browser runtimes from the Extension.js cache.
uninstall removes browser runtimes that Extension.js downloaded into its managed cache. It never removes your system browser, and it never removes an extension installed in a browser. To remove a development extension, stop the dev session. The extension was loaded into a managed browser profile, not into your own browser profile.

When to use uninstall

  • You want to reclaim disk space from managed browsers you no longer need.
  • You are resetting a managed browser install to force a fresh download on next install.
  • You are cleaning up continuous integration (CI) caches or switching browser targets.

Canonical usage

For a single browser, use the positional form:
Use --all to remove every managed browser target.

Usage

Arguments and flags

--all removes the same managed set that install --browser all creates: chrome, chromium, edge, and firefox.

Machine output with --output json

--output json prints one schema-1 envelope on stdout:
  • A successful removal prints a status: "uninstalled" frame naming the target in value.
  • --where prints a status: "located" frame with the resolved paths in value.paths.
  • A failed removal prints ok: false with error.code: "E_BROWSER_UNINSTALL" before the process exits 1.

Examples

Remove managed Chrome for Testing

Remove all managed browsers

Show the managed uninstall path for Firefox

Best practices

  • Use --all in CI teardown to clean up managed browsers after test runs.
  • Use --where first to confirm what will be removed before scripting bulk uninstalls.

Behavior notes

  • If you set EXT_BROWSERS_CACHE_DIR, uninstall uses that custom cache root.

Next steps