package-info.nvim
paq-nvim
package-info.nvim | paq-nvim | |
---|---|---|
3 | 28 | |
443 | 632 | |
- | - | |
3.8 | 7.5 | |
3 months ago | 3 months ago | |
Lua | Lua | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
package-info.nvim
-
Node package check
Nice! Another option is https://github.com/vuki656/package-info.nvim
-
What are good general guidelines/tips for someone writing a plugin in Lua?
Keep the code splitting simple. When i was writing initial version of package-info I split stuff into multiple files, tried to make it all "nice" and organized. What that did is just complicated things and when and
-
🚀 Package-info 2.0 released. Delete, update, install new, install specific versions of packages. GIFs inside.
TLDR: besides showing outdated npm packages as virtual text, now you can install new, delete, update to the latest, change the version to specific. Check the docs here. And the breaking change note here.
paq-nvim
- [Neovim] Gestionnaire de packages basé à Lua
-
Is Packer still maintained?
If you want a dead simple package mamage that only puts packages in opt and start, you can use paq.nvim
-
Introducing LazyVim!
Is there anyone here who can share some feedback on how much lazy.nvim has been better than what you were using previously? If my context helps, I'm using paq-nvim, previously was using packer.
- Neovim - Workflow para Java, C# e JS/TypeScript (Atualização com Neovim 0.8 e LSP)
-
Cannot update plugins
This was a problem when I was using paq as my manager, now I have the same problem with packer. It never happened when I wanted to install new plugins, only on updating. With packer I have a workaround: after it fails to sync it allows to re-run all failed jobs, and each times about a half of failed jobs fail again, others update successfully, so I can iteratively sync everything, but that's a terrible waste of time;
-
Help with plug
Options: - packloadall command family and maybe git submodules - minpac which is a thin utility around the above - vim-plug - old but still popular for it does the job - packer.nvim is a popular choice for lua configs, never got to using it myself - paq-nvim is another often mentioned lua solution - dozens of other solutions
-
which plugin manager are you using?
that sounds like paq, but slow?
-
New to Rust. How to setup Nvim as IDE?
On my Neovim setup, I simply have the following plugins. I use paq as a plugin manager:
-
Neovim: Plugins to get started
paq.nvim
What are some alternatives?
orgmode - Orgmode clone written in Lua for Neovim 0.9+.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
crates.nvim - A neovim plugin that helps managing crates.io dependencies
awesome-neovim - Collections of awesome neovim plugins.
baleia.nvim - Colorize text with ANSI escape sequences (8, 16, 256 or TrueColor)
targets.vim - Vim plugin that provides additional text objects
orgmode.nvim - Orgmode clone written in Lua for Neovim 0.7+. [Moved to: https://github.com/nvim-orgmode/orgmode]
nvim-compe - Auto completion Lua plugin for nvim
which-key.nvim - 💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.
lazy.nvim - 💤 A modern plugin manager for Neovim