How do I migrate from Packer.nvim to Paq-nvim?

Replace your Packer setup with Paq's require statement in init.lua, listing plugins with Paq's syntax for options like build or opt. Then run :PaqSync to install plugins; note that Paq uses different option formats, so adjust commands accordingly.

Paq-nvim vs Lazy.nvim: which should I choose?

Paq-nvim excels in simplicity and speed with concurrent operations, while Lazy.nvim offers more features like lazy loading and dependency management. Choose Paq for a minimal, fast setup; opt for Lazy if you need advanced lazy loading or ecosystem tools.

How to install plugins from a private Git repository with Paq?

Use the 'url' option in the plugin specification to provide the full Git URL, e.g., { 'my-plugin', url = 'https://gitlab.com/user/repo.git' }. Ensure git is configured with credentials for private access, as Paq relies on git for cloning.

Can Paq handle post-install build scripts?

Yes, via the 'build' option, which can be a string shell command, a Lua function, or a Vim command prefixed with ':'. For example, { 'plugin', build = ':TSUpdate' } runs a Vim command after install/update, as shown in the README.

Is Paq-nvim good for large plugin configurations?

Paq's concurrent installation makes it efficient for many plugins, but its minimal design might lack optimizations for startup time or dependency resolution. For large configs, test performance with :PaqSync and consider if missing features are critical.

How to clean up unused plugins automatically?

Run the :PaqClean command to remove all packages in Paq's directory not listed in your configuration. This helps maintain a tidy setup without manual deletion, part of the sync workflow.

paq-nvim — Lightweight Neovim Package Manager

What is paq-nvim?

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.

Target Audience

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.

Value Proposition

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

Use Cases

Best For

Managing Neovim plugins with a Lua-based configuration for simplicity and integration.
Users needing fast, concurrent installation and updates of plugins leveraging Neovim's event-loop.
Developers who prefer a lightweight package manager with a minimal codebase of around 500 lines.
Scenarios requiring flexible plugin options such as custom builds, optional loading, pinning, or non-GitHub repositories.
Automating plugin management with a single sync command to install, update, and clean packages.
Neovim users on the latest stable version seeking an efficient, no-frills package manager focused on performance.

Not Ideal For

Users on older Neovim versions (e.g., Debian Stable) who cannot upgrade, as they must rely on an unsupported branch with no backports.
Developers needing graphical interfaces, advanced dependency resolution, or extensive plugin management features beyond basic install/update/clean operations.
Projects requiring automated, CI/CD-integrated plugin updates without manual intervention in a Neovim session.

Pros & Cons

Pros

Simple Configuration

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.

Concurrent Performance

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.

Minimal Footprint

With around 500 lines of code, the codebase is lightweight and easy to audit or modify, contributing to its simplicity and low overhead.

Flexible Plugin Options

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.

Cons

Version Compatibility Issues

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.

Limited Advanced Features

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.

Manual Bootstrapping Complexity

Automatic installation or headless mode setup requires consulting additional documentation (:h paq-bootstrapping), adding extra steps for users seeking hands-off initialization.

What is paq-nvim?

Target Audience

Value Proposition

Use Cases

Best For

Managing Neovim plugins with a Lua-based configuration for simplicity and integration.
Users needing fast, concurrent installation and updates of plugins leveraging Neovim's event-loop.
Developers who prefer a lightweight package manager with a minimal codebase of around 500 lines.
Scenarios requiring flexible plugin options such as custom builds, optional loading, pinning, or non-GitHub repositories.
Automating plugin management with a single sync command to install, update, and clean packages.
Neovim users on the latest stable version seeking an efficient, no-frills package manager focused on performance.

Not Ideal For

Users on older Neovim versions (e.g., Debian Stable) who cannot upgrade, as they must rely on an unsupported branch with no backports.
Developers needing graphical interfaces, advanced dependency resolution, or extensive plugin management features beyond basic install/update/clean operations.
Projects requiring automated, CI/CD-integrated plugin updates without manual intervention in a Neovim session.

Pros & Cons

Pros

Simple Configuration

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.

Concurrent Performance

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.

Minimal Footprint

With around 500 lines of code, the codebase is lightweight and easy to audit or modify, contributing to its simplicity and low overhead.

Flexible Plugin Options

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.

Cons

Version Compatibility Issues

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.

Limited Advanced Features

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.

Manual Bootstrapping Complexity

Automatic installation or headless mode setup requires consulting additional documentation (:h paq-bootstrapping), adding extra steps for users seeking hands-off initialization.

paq-nvim

What is paq-nvim?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

paq-nvim

What is paq-nvim?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?