A modern, declarative plugin manager for Neovim with lockfile support and no compilation step.
pckr.nvim is a plugin manager for Neovim that allows users to declaratively specify, install, and manage their Neovim plugins. It solves the problem of organizing and maintaining plugins in a reproducible way, with features like lockfile support and lazy loading to enhance performance and reliability.
Neovim users who want a modern, efficient way to manage their plugin ecosystem, especially those migrating from packer.nvim or seeking lockfile capabilities and lazy loading.
Developers choose pckr.nvim for its clean, refactored codebase, lockfile support for version pinning, and absence of compilation steps, making it a reliable and performant successor to packer.nvim.
Spiritual successor of https://github.com/wbthomason/packer.nvim
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables clean, structured plugin specification in Lua tables, as shown in the README where plugins are defined with keys like 'cond' for lazy loading and 'config' for setup.
Provides reproducible setups by pinning plugin versions with :Pckr lock and restore commands, a key feature emphasized in the README for consistency across environments.
Boosts startup time by loading plugins on-demand using helper functions like cmd() and keys(), with examples for commands and keymaps in the quickstart.
Allows running shell commands, Neovim commands, or Lua functions after updates, demonstrated with examples such as ':TSUpdate' for nvim-treesitter.
Requires Neovim v0.9 or newer, excluding users on older versions who may not be ready to upgrade, as stated in the requirements section.
On Windows 10, local plugins need developer mode enabled for symbolic links, adding an extra administrative step that complicates setup.
Auto-installation requires a custom bootstrap function in the config, which is more involved than plug-and-play solutions and can be error-prone for beginners.
The README includes a 'TODO' in the dependencies section, indicating incomplete explanations that might leave users confused about advanced features.