Coverage in macCurrent 1.2.0.65

Find the right update path for your packages and plug-ins.

Choose a focused guide for npm tools, Python environments, Go executables or editor extensions. See what macCurrent can update and when a host app or vendor is needed.

Updated October 27, 2026 · ~4 min read

macCurrent native Mac interface showing Applications alongside expanded npm packages and plug-in categories
Native macOS interface captured from the release preparation build. Open the image to view it at full size.

Quick guide

The short answer

macCurrent checks and updates supported packages and plug-ins alongside Mac apps. npm tools, Python environments, standalone Go tools and editor add-ons have different update paths. Use the dedicated guide for the installed copy you want to change. Obsidian plug-ins remain tied to a vault; audio plug-in installation may need the vendor updater.

Choose your package or editor guide

For the coverage described here, use macCurrent 1.2.0.65 or later. Screenshots show a release preparation build.

Global npm tools: choose compatible Node/npm tools and update the intended global installation.

Python packages: review the environment, manager and existing project lock file.

Standalone Go tools: check eligible gopls and govulncheck installations and compiler requirements.

VS Code extensions and JetBrains plug-ins: review compatible releases, editor profiles, pinned extensions and IDE restart steps.

Developer package overview: compare supported Rust/Cargo, Composer and Homebrew routes too.

Use case: update an Obsidian plug-in in the intended vault

You keep separate Obsidian vaults for work notes and personal writing. The same community plug-in is installed in both, but you only want to update the work copy.

  1. Select the discovered plug-in and confirm its vault and owning Obsidian installation.
  2. Review its eligible community release and use Update Now. Close the owning app when prompted.
  3. Check the installed result for that vault.

Supported updates preserve plug-in settings and enabled state, while the other vault’s plug-in remains a separate installation.

Custom or private plug-in sources may need their own manager. A matching display name alone does not establish the source.

Audio plug-ins and other software components

macCurrent inventories supported AU, VST, VST3, CLAP and AAX audio plug-ins, along with supported photo and video plug-ins. A discovered format does not establish a verified update or direct installation.

For example, a music project may use a commercial VST3 instrument while a photo workflow uses Adobe Camera Raw. Follow the selected item’s action: a vendor installer, account or Adobe Creative Cloud can be required. Keep projects, presets and settings backed up separately.

Frequently asked questions

Can every discovered package or plug-in update in macCurrent?

No. Installation depends on the source, runtime or host compatibility and the exact installed copy. Some items need their package manager, editor or vendor updater.

Where are the detailed npm and editor guides?

The npm package guide covers global tools and Node.js compatibility. The VS Code and JetBrains guide covers editor profiles, pinned-extension updates and eligible IDE plug-ins. Both include developer scenarios and practical steps.

Can macCurrent update an Obsidian plug-in in one vault?

Eligible Obsidian community plug-ins update within the selected vault. Settings and enabled state are preserved, and other vault copies remain separate installations.

Are audio plug-ins included in automatic installation?

Inventory support alone does not establish a direct installer. A verified release source is needed for update checks, and installation may require the vendor’s installer or account.

Related macCurrent guides

Find and install supported Mac app updates

Review updates from several sources and install supported updates in one place. Free during the current preview.