Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/tips.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ Most of your lazy.nvim plugin specs will work as-is with zpack. However, zpack f
- **version pinning**: lazy.nvim's `version` field maps to zpack's `sem_version`. See [Spec Reference](spec.md) and [version pinning examples](examples.md#version-pinning-for-lazynvim-compatibility)
- **dev mode**: Use `src = vim.fn.expand('~/projects/my_plugin.nvim')` for local development
- **profiling**: Use `nvim --startuptime startuptime.log`. Also refer to example [Neovim Profiler script](https://gist.github.com/zuqini/35993710f81983fbfa6baca67bdb32ed)
- **install/update feedback**: `vim.pack` surfaces progress via `:messages` (e.g. `vim.pack: Downloading updates (0/83)`) instead of a dedicated UI. These messages are hidden if you have `vim.opt.cmdheight = 0` — raise it, check `:messages`, or route them through a notifier like [snacks.notifier](https://github.com/folke/snacks.nvim), [nvim-notify](https://github.com/rcarriga/nvim-notify), or [noice.nvim](https://github.com/folke/noice.nvim)
- **passive libraries**: lazy.nvim's community specs silently force utility libraries like `plenary.nvim` to `lazy = true` regardless of your config. zpack respects your spec as-written, so set `lazy = true` explicitly on pure-dependency plugins you don't want eager-loaded

## Compatibility Notes

Expand Down
Loading