VSCode 拡張機能のバージョンを確認する方法 This article explains how to check the version of installed VSCode extensions using both t…

Knowing exactly which version of a Visual Studio Code extension is installed is a small but frequently overlooked detail that can save hours of troubleshooting. When an editor feature suddenly behaves differently, a linter stops recognizing valid syntax, or a plugin breaks after an automatic update, the extension's version number is often the first piece of information needed to diagnose the problem, roll back a change, or file a useful bug report. It also matters for teams trying to keep development environments consistent across multiple machines.

The most direct way to check a version is through the graphical interface. Opening the Extensions view, either from the activity bar on the left or with the keyboard shortcut Ctrl+Shift+X on Windows and Linux or Cmd+Shift+X on macOS, lists every installed extension. Selecting an individual extension opens its details page, where the version number is displayed near the extension name and publisher, alongside the changelog and feature documentation. This view is useful when you want context, since it also shows whether an update is available and links to the release notes that explain what changed between versions.

For anyone who prefers the terminal or needs to inspect many extensions at once, the command line is faster. Running the command code with the arguments to list extensions and show versions returns every installed extension together with its version in a compact format, typically written as publisher.extension-name followed by an at sign and the version string. This assumes the code command is available on your system path, which VS Code can configure through its command palette option to install the shell command. The command-line approach is particularly valuable for scripting, because the output can be captured, compared, or committed to a repository as a record of a known-good setup.

That capacity for automation is where version checking connects to broader environment-management practices. Because the list command produces plain text, teams can save it to a file and diff it against another developer's environment to spot mismatches. VS Code also supports a workspace file, commonly named extensions.json inside a .vscode folder, that recommends extensions for a given project, though it records identifiers rather than pinning exact versions. For stricter reproducibility, many teams pair VS Code with development containers, where the extensions and their versions are declared in configuration and rebuilt identically on every machine. In those setups, confirming installed versions helps verify that the container matches expectations.

VS Code's extension model itself provides useful background for interpreting these version numbers. Extensions are distributed through the Visual Studio Code Marketplace, and each carries a manifest that declares, among other things, the range of editor versions it supports through an engines field. When the editor updates but an extension has not been rebuilt for the new API, compatibility problems can appear, which is precisely when comparing the extension version against the editor version becomes important. VS Code generally installs the latest compatible release automatically, but it also offers a way to install an earlier build. Right-clicking an extension in the Extensions view reveals an option to install another version, letting users pin to a specific release that is known to work while a newer one is investigated or a regression is reported upstream.

A few related details are worth keeping in mind. Some extensions publish pre-release versions that can be toggled on, and these will appear with their own version numbers, so it is worth confirming whether you are running a stable or pre-release build. Extension packs, which bundle several extensions under a single entry, will show the pack's version rather than the versions of each component, meaning the individual members still need to be checked separately. Editors built on the same open-source base, such as some VS Code-compatible forks, may use a different marketplace and command name, so the exact versions available can differ from the official distribution.

Taken together, these methods form a simple but practical toolkit. The graphical view is best for quick, context-rich inspection of a single extension, while the command line suits audits, scripting, and documenting environments. Combined with recommended-extensions files and container-based workflows, routinely verifying extension versions is a low-effort habit that makes compatibility issues easier to trace and development environments easier to reproduce.