NPM Visual Manager

A Visual Studio Code extension that provides a visual interface for managing NPM dependencies, inspired by the NuGet Package Manager in Visual Studio.
Screenshots

Features
| Category |
Capabilities |
| Dependency Management |
Visual table with sorting (including by update type), filtering by name and by update type (Major/Minor/Patch), auto-refresh on package.json changes |
| Search & Install |
NPM registry search with debouncing, install as regular or dev dependency |
| Updates |
One-click individual or bulk updates, version rollbacks, ignore packages from checks, AI update prompt for coding assistants |
| Security & Info |
Security audit integration, deprecation warnings, package sizes, direct links to changelogs, "why is it installed?" reverse dependency view |
| Multi-Project |
Auto-detection in monorepos, project selector showing each package.json path, supports npm, yarn, pnpm, and bun |
| Localization |
8 languages: Spanish, German, French, Chinese (Simplified), Japanese, Portuguese, Russian, Korean |
| UI |
Native VS Code theme integration, customizable columns, activity bar badge with pending updates/vulnerabilities |
Requirements
- VS Code 1.86.0 or higher
- Node.js project with a
package.json file
- Package manager installed (npm, yarn, pnpm, or bun)
Installation
Install from the VS Code Marketplace or search for "NPM Visual Manager" in the Extensions panel (Ctrl+Shift+X).
Also available on Open VSX Registry for VSCodium and other compatible editors.
Usage
Opening the Package Manager
- Command Palette: Press
Ctrl+Shift+P (or Cmd+Shift+P on Mac) and type "Open NPM Package Manager"
- Context Menu: Right-click on
package.json in the Explorer and select "Open NPM Package Manager"
Managing Dependencies
- View Dependencies: The table shows all packages with their installed and latest versions
- Check for Updates: The extension automatically checks npm registry for latest versions
- Update Packages:
- Click "Update" on individual packages
- Use "Update All" button to update all outdated packages at once
Which package.json is being managed
Repos often hold more than one package.json (a monorepo, a WordPress theme plus its plugins, a site with its own build folder). The header always shows the target file as a path chip next to the project selector; click it to open that file. The editor tab title, every confirmation dialog and every progress notification name the same path, so an update can never land on a file you did not expect. When several projects are detected, the selector switches between them and the "Updates" view lists the pending updates per package.json. Projects are discovered up to five folder levels deep; if one of yours is missing, raise npm-visual-manager.scan.maxDepth.
Filtering
- Search: Type in the filter box to search by package name or declared version
- Update type: Click the Major, Minor, Patch (and Pre-release/Stable, when present) chips next to the filter box to show only those updates. Chips can be combined, and each shows how many pending updates it covers. Click an active chip again to clear it.
- Sorting: Click a column header to sort; click it again to reverse. Sorting by Update lists Major first, then Minor, Patch, Stable promotions and Pre-releases.
"Update All", "Select all" and the update counter apply only to the packages currently visible, so you can, for example, filter by Patch and update just the patches.
Search & Install Packages
Expand the "INSTALL PACKAGES" section, type a package name (min. 2 characters), and click on a result to install it. You can choose to install as a regular dependency or dev dependency.
Smart Detection: When searching for a package that is already installed in your project, the button will change to "Uninstall" with a confirmation dialog.
Ignore Packages
Click the eye icon 👁️ next to any package to ignore it from update checks. Ignored packages won't appear in the "updates available" counter. Click "Show All Packages" to toggle between viewing only outdated packages or all packages.
Changelog Viewer
Hover over any package row and click the book icon 📖 to open the package's GitHub releases page. This helps you review what changed before updating.
AI Update Prompt
Prefer to let an AI coding assistant (Copilot, Cursor, Claude, etc.) handle the updates? Click AI prompt in the toolbar to copy a Markdown prompt with the pending updates currently visible in the table, so you can combine it with the filters above (for example, only Major updates). A notification lets you also open it in an editor tab.
The prompt lists each package with its declared, installed and target version, groups them from lowest to highest risk (Patch, Minor, Major, Pre-release), and includes the exact command for your package manager. Pre-release targets and breaking 0.x bumps go to the riskier groups, and packages from the same repository (such as react and react-dom) are flagged to be updated together. It tells the assistant to update majors one at a time, read their release notes and run the project's lint, test, build or typecheck scripts after each step.
The prompt never includes registry URLs or links to non-GitHub repositories, so internal hosts from private registries are not shared with an external AI service. Release notes are linked, not summarized: the assistant has to open them to check for breaking changes.
Private registries (including GitLab)
Version checks, version selection and package search read the selected project's npm configuration: project/workspace .npmrc, user .npmrc, global npm configuration and NPM_CONFIG_* environment overrides. Scoped packages use their @scope:registry mapping; other packages use the default registry.
For example, a GitLab project feed can be configured in the project's .npmrc:
@company:registry=https://gitlab.example.com/api/v4/projects/42/packages/npm/
Keep authentication in your user .npmrc or use an environment variable available to the VS Code extension host:
//gitlab.example.com/api/v4/projects/42/packages/npm/:_authToken=${NPM_TOKEN}
GitLab group and instance npm endpoints are supported too. The extension reuses npm authentication and its proxy/CA configuration (https-proxy, cafile, etc.); it does not ask for or store tokens in extension settings. Install and update commands continue to use the selected package manager's own configuration. Native Yarn .yarnrc.yml registry settings are not imported by these metadata queries; use npm-compatible .npmrc settings for them.
GitLab lookup uses the full package name, such as @company/ui-kit, because its npm API does not provide the public npm text-search endpoint. General text searches use the configured default registry. A private lookup never falls back to npmjs.org on authentication or lookup errors. A GitLab server may independently forward requests according to its own configuration.
The package-name tooltip shows the resolved registry, and its link points to that registry. Metadata caches are isolated by project and registry. Click Refresh after editing .npmrc or changing tokens to reload configuration immediately (configuration is otherwise cached for up to 30 seconds). If credentials use environment variables, restart VS Code after changing its launch environment. See GitLab's npm registry documentation for token permissions and endpoint formats.
The registry libraries require the Node.js runtime bundled with VS Code 1.86 or newer.
Extension Settings
This extension contributes the following settings:
npm-visual-manager.columns.size: Show Size column
npm-visual-manager.columns.type: Show Type column
npm-visual-manager.columns.lastUpdate: Show Last Update column
npm-visual-manager.columns.security: Show Security column
npm-visual-manager.columns.semverUpdate: Show Update Type column
npm-visual-manager.badge.enabled: Show a badge on the activity bar icon with the number of available updates and vulnerable packages
npm-visual-manager.scan.maxDepth: How many folder levels below the workspace root are searched for package.json files (default 5)
npm-visual-manager.scan.excludeFolders: Folder names never searched (defaults to node_modules, bower_components, vendor, uploads, dist, out, coverage, tmp, temp; dotted folders are always skipped)
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License - see LICENSE file for details.
Acknowledgments
- Inspired by Visual Studio's NuGet Package Manager
- Uses VS Code Webview UI Toolkit design principles
- Built with React and Vite