package-info.nvim
A Neovim plugin that displays npm/yarn/pnpm/bun dependency versions as virtual text and provides quick commands for package management.
What is package-info.nvim?
package-info.nvim is a Neovim plugin that provides inline visual feedback and quick actions for managing JavaScript/TypeScript package dependencies. It displays the latest available versions of dependencies directly in the `package.json` file as virtual text and allows developers to update, delete, install, or change dependency versions without leaving the editor. It solves the problem of constant context switching between the editor and terminal for routine package management tasks.
Neovim users who work on JavaScript, TypeScript, or Node.js projects and frequently manage dependencies using npm, yarn, pnpm, or bun. It's particularly useful for developers who want to streamline their workflow and reduce terminal usage.
Developers choose package-info.nvim because it integrates package management directly into Neovim, saving time and reducing context switching. Its automatic package manager detection, virtual text display, and one-click actions provide a seamless experience compared to manually running CLI commands.
Overview
✍️ All the npm/yarn/pnpm commands I don't want to type
Use Cases
Best For
- Quickly checking for outdated dependencies while editing package.json
- Updating a single dependency to its latest version without terminal commands
- Managing dependencies in monorepos or large projects with multiple packages
- Adding or removing packages during development without interrupting flow
- Visualizing dependency status directly in the editor with color-coded virtual text
- Integrating package management status into custom Neovim status bars
Not Ideal For
- Teams using editors other than Neovim, such as VS Code or JetBrains IDEs, where this plugin has no integration.
- Projects that rely on automated CI/CD pipelines for dependency updates, making inline manual updates redundant or risky.
- Developers working with extremely large dependency lists where the `npm outdated` command is too slow, as admitted in the README.
- Users needing advanced package management features like batch updates, dependency graph visualization, or support for non-JS package managers.
Pros & Cons
Pros
Displays the latest available versions of dependencies directly in `package.json` as virtual text, using color-coded highlights for up-to-date, outdated, and invalid packages based on `npm outdated --json` output.
Allows updating, deleting, or installing dependencies with a single keystroke, automatically detecting the project's package manager from lockfiles like `yarn.lock` or `package-lock.json`.
Provides a `get_status()` function that can be integrated into custom status bars like Galaxyline or Feline, offering real-time loading feedback for plugin operations.
Includes a Telescope extension for browsing and managing dependencies in a visual, searchable interface, inspired by telescope-lazy.nvim, enhancing usability beyond inline text.
Cons
The README explicitly warns that display can be slow on projects with many dependencies due to the external `npm outdated --json` command, with no built-in optimization beyond caching.
Offers no default keybindings, requiring users to manually set up mappings for all actions, which can be tedious and error-prone for newcomers.
Marked as beta with a migration notice for config changes, indicating potential breaking updates and less reliability compared to stable plugins.
Only supports npm, yarn, pnpm, and bun, leaving out other package managers or languages, which restricts its utility in polyglot projects.
Frequently Asked Questions
Related Projects
crates.nvimA neovim plugin that helps managing crates.io dependencies
import.nvimAn import picker that learns from your codebase
projektgunnar.nvimGunnar is the nice old Swedish man who helps you add projects or packages to dotnet solutions so you can take a Fika(tm) instead of having to remember how to do the different dotnet commands.
LazyDeveloperHelperToo lazy for write "pip install -r requirements.txt", or "cargo add ...".. or maybe.. "luarocks install .." and writing it to requirements file? This plugin for you!
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.