lazy.nvim README

The project's README from github.com/folke/lazy.nvim. As one markdown file: README.md.

Install · Configure · Docs

Latest release Last commit License Stars Issues Repo Size follow on Twitter

lazy.nvim is a modern plugin manager for Neovim.

image

✨ Features

⚡️ Requirements

🚀 Getting Started

Check the documentation website for more information.

lazy.nvim (folke/lazy.nvim)

neovim-plugin
Searching Database…

21.7K ·GitHub
What is this?lazy.nvim is a modern plugin manager for Neovim. It installs and updates your plugins, shows them in a built-in UI, and keeps startup fast through automatic caching, bytecode compilation and lazy-loading.
Is this a separate program I install, or something that lives inside Neovim?It lives inside Neovim: lazy.nvim is itself a Neovim plugin, written in Lua, that you add to your config. From there it manages all your other plugins.
How do I set it up?You add lazy.nvim to your Neovim config; after that it installs any missing plugins automatically before Neovim starts, so you can use it right away. The full walkthrough is on the documentation website.
What does my machine need for it to work?Neovim 0.8.0 or newer built with LuaJIT, plus Git 2.19.0+ for partial clones. A Nerd Font is optional, and luarocks is only needed for rockspecs — you can disable that by removing rockspec from opts.pkg.sources.
Does it run on Windows too, or only on macOS and Linux?It runs wherever Neovim runs, so Windows, macOS and Linux are all covered — it is a Lua plugin inside the editor, not a native binary.
How does it keep startup times fast?It caches and bytecode-compiles Lua modules, lazy-loads plugins on events, commands, filetypes and key mappings, runs work asynchronously, and even lazy-loads colorschemes automatically. Partial clones instead of shallow clones also make installs lighter.
Can I pin my plugins to exact versions?Yes — lazy.nvim supports commits, branches, tags, versions and full Semver, and writes a lazy-lock.json lockfile to track what is installed. It also checks for updates automatically, with a statusline component showing how many are pending.
I'm developing my own plugin — can it load a local copy instead of a published repo?Yes, there are dev options and patterns for using local plugins, so you can work on your own plugin through lazy.nvim like any other.
Does all my plugin config have to sit in one file?No, configuration can be split across multiple files. As a bonus, lazy.nvim generates helptags from the headings of plugins' README.md files when a plugin ships no vimdocs.
Creator
folke
Size
3.1 MB
Stars
21.7K
Age
3y
Commits · 90 Days