Live Lib - npm Library Manager

English | 한국어

A VS Code extension for managing npm libraries in your project.

Features

• View Library List: See all project dependencies at a glance
• View Details: Check description, version, and homepage information for each library
• Update Availability: Compare with the latest version to see which libraries can be updated
• Update Libraries: Update to the latest version. Major updates outside your package.json range ask for confirmation first and offer the latest version within the range instead
• Detect Unused Libraries: Identify libraries that are not actually used in the project
• Delete Libraries: Remove unnecessary libraries
• Monorepo Support: Shows the root and each workspace package side by side (npm, yarn and bun workspaces, pnpm pnpm-workspace.yaml)

Usage

1. Click the Live Lib icon in the Activity Bar of VS Code.

2. All libraries in your project will be displayed.

3. Click a library to see its details, or use the buttons that appear when you hover over it:

   • Show Details: View library information
   • Update: Update to the latest version (shown only when a newer version exists)
   • Delete: Remove the library
   

4. Latest versions from the npm registry are cached for 6 hours, even across VS Code restarts. Click the refresh button at the top of the view to check the registry again right away.

Requirements

• VS Code 1.74 or later
• Node.js project (requires package.json file)
• npm, pnpm, yarn or bun. The package manager is detected from the packageManager field in package.json or from the lockfile, and Update / Delete run the matching command (for example pnpm add / pnpm remove).

Monorepos

If the root package.json has workspaces (npm, yarn, bun) or the folder has a pnpm-workspace.yaml (pnpm), the folder in the tree lists (root) and each workspace package, such as apps/web or packages/ui. Expand a package to see its libraries.

• Update and Delete run in that package's folder, so only its package.json changes.
• Installed versions are found in the package's node_modules or, when hoisted, in the root node_modules.
• A package's libraries are checked for usage in that package's folder only. Libraries in the root package.json are checked across the whole repository, since workspace packages often import shared dependencies declared at the root.

Private and Custom Registries

Latest versions are looked up in the registry set in .npmrc (registry= and @scope:registry=), read from your home folder and from the project up to the repository root. The closest file wins.

Live Lib never sends credentials such as _authToken. Packages from a registry that requires authentication show "Latest: not available" in the tooltip.

Language

The interface follows VS Code's display language. English is the default, and Korean is available when VS Code is set to Korean.

Extension Settings

Known Issues

• Usage detection looks at import / require statements, package.json scripts and config files. Imports built from variables (for example require(name)) cannot be detected.
• A devDependency with no usage found is shown as not detected instead of unused, because tools are often used indirectly (for example webpack-cli through webpack). Check these before removing them.
• The usage scan skips build output folders such as dist, build, out and coverage at any depth, plus folders listed in .gitignore. Source code kept in a folder with one of those names (for example src/build/) is not scanned.

Feedback

• Found a bug or have an idea? Open an issue on GitHub.
• If Live Lib saves you time, a rating on the Marketplace helps other developers find it.

Release Notes

See CHANGELOG.md.