*lazy.nvim.txt* For NVIM v0.5.0 Last change: 2022 December 13 ============================================================================== Table of Contents *lazy.nvim-table-of-contents* 1. lazy.nvim |lazy.nvim-lazy.nvim| - Features |lazy.nvim-features| - TODO |lazy.nvim-todo| - Differences with Packer |lazy.nvim-differences-with-packer| - Other Neovim Plugin Managers in Lua|lazy.nvim-other-neovim-plugin-managers-in-lua| ============================================================================== 1. lazy.nvim *lazy.nvim-lazy.nvim* FEATURES *lazy.nvim-features* TODO *lazy.nvim-todo* - fancy UI to manage all your Neovim plugins - auto lazy-loading of lua modules - lazy-loading on events, commands, filetypes and key mappings - Partial clones instead of shallow clones - waits till missing deps are installed (bootstrap Neovim and start using it right away) - Async - No need to manually compile - Fast. Automatically caches and compiles byte code of all lua modules needed during startup - Correct sequencing of dependencies (deps should always be opt. Maybe make everything opt?) - Config in multiple files - dev option and patterns for local packages - Profiling - lockfile `lazy-lock.json` - upvalues in `config` & `init` - check for updates - commit, branch, tag, version support - semver https://devhints.io/semver - auto-loading on completion for lazy-loaded commands - bootstrap code - Background update checker - statusline component to see number of pending updates - health checks: check merge conflicts async - unsupported props or props from other managers - other packages still in site? - other package manager artifacts still present? compiled etc - status page showing running handlers and cache stats - temp colorscheme used during startup when installing missing plugins - automatically reloads when config changes are detected - handlers imply opt - dependencies imply opt for deps - show spec errors in health - fix plugin details - show disabled plugins (strikethrough?) - log file - git tests - Import specs from other plugin managers - packspec - add support to specify `engines`, `os` and `cpu` like in `package.json` - semver merging. Should check if two or more semver ranges are compatible and calculate the union range - default semver merging strategy: if no version matches all, then use highest version? - package meta index (package.lua cache for all packages) DIFFERENCES WITH PACKER *lazy.nvim-differences-with-packer* - **Plugin Spec**: - `setup` => `init` - `requires` => `dependencies` - `as` => `name` - `opt` => `lazy` - `run` => `build` - `lock` => `pin` - `module` is auto-loaded. No need to specify OTHER NEOVIM PLUGIN MANAGERS IN LUA*lazy.nvim-other-neovim-plugin-managers-in-lua* - packer.nvim - paq-nvim - neopm - dep - optpack.nvim - pact.nvim Generated by panvimdoc vim:tw=78:ts=8:noet:ft=help:norl: