A simple, fast, and lightweight Neovim package manager written in Lua.
Paq-nvim is a Neovim package manager written in Lua that efficiently manages plugins within the Neovim ecosystem. It leverages Neovim's event-loop for concurrent operations, making it fast and lightweight. It solves the problem of plugin management by providing a simple, performant tool with a minimal codebase.
Neovim users, particularly those on the latest stable version, who want a Lua-based, concurrent package manager for managing their plugin configurations. It is suitable for developers who prefer a lightweight, straightforward setup without unnecessary complexity.
Developers choose Paq-nvim for its simplicity, speed due to concurrent operations using Neovim's event-loop, and small codebase of around 500 lines. Its unique selling point is the single sync command that installs, updates, and cleans packages in one go, along with flexible options like custom builds and non-GitHub repository support.
🌚 Neovim package manager
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Setup involves a single Lua require statement with plugin lists, making integration into existing Neovim configs straightforward without complex boilerplate, as shown in the README's usage example.
Leverages Neovim's event-loop for parallel installation and updates, speeding up plugin management significantly compared to sequential approaches, as highlighted in the features list.
With around 500 lines of code, the codebase is lightweight and easy to audit or modify, contributing to its simplicity and low overhead.
Supports various options like custom builds (via string or function), optional loading, pinning, and non-GitHub URLs, offering versatility for diverse plugin needs, as detailed in the options table.
Requires Neovim's latest stable version; users on older systems must use a separate 'debian' branch that is not maintained with backports, risking bugs without fixes, as noted in the README.
Lacks built-in dependency management, version locking beyond basic pinning, or GUI tools, which might be insufficient for complex plugin ecosystems compared to more comprehensive managers.
Automatic installation or headless mode setup requires consulting additional documentation (:h paq-bootstrapping), adding extra steps for users seeking hands-off initialization.