package-info.nvim
plugin-template.nvim
| package-info.nvim | plugin-template.nvim | |
|---|---|---|
| 3 | 6 | |
| 443 | 101 | |
| - | - | |
| 3.8 | 0.0 | |
| 2 months ago | 5 months ago | |
| Lua | Lua | |
| GNU General Public License v3.0 only | - |
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.
plugin-template.nvim
-
Arduino.nvim
I was put off by the complexity of adding tests but in the add I got it setup in my plugin by downloading a plugin template and copying the way everything is done. Probably this one https://github.com/m00qek/plugin-template.nvim
-
Some questions about Lua plugin development
Hey, I have put together a template for Neovim plugins that proposes a structure and have a good setup for tests. Take a look, it might inspire you https://github.com/m00qek/plugin-template.nvim
-
What are good general guidelines/tips for someone writing a plugin in Lua?
Hello everyone, I created a plugin template for Neovim before and now I'm planning to add a general guidelines section to its documentation. To not make this too personal I'd like to hear from you what are good tips, guidelines, do/don't, etc. when writing a Lua plugin. Does anyone here have strong opinions on this?
-
Help with a Lua plugin
I suggest you to add some tests to it, which will ensure that it keeps working when you add more stuff to if in the future. One way is to do setup them like in https://github.com/m00qek/plugin-template.nvim
- A template for plugins written mostly in Lua
-
How do you build unit tests for your lua plugins?
I had the same trouble recently so I put together a template with the solution I found: https://github.com/m00qek/plugin-template.nvim
What are some alternatives?
orgmode - Orgmode clone written in Lua for Neovim 0.9+.
nvim-comment - A comment toggler for Neovim, written in Lua
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
plenary.nvim - plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.
crates.nvim - A neovim plugin that helps managing crates.io dependencies
baleia.nvim - Colorize text with ANSI escape sequences (8, 16, 256 or TrueColor)
boilit - create boilerplate structure for neovim plugins
orgmode.nvim - Orgmode clone written in Lua for Neovim 0.7+. [Moved to: https://github.com/nvim-orgmode/orgmode]
vim-lsp - async language server protocol plugin for vim and neovim
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.
Dash-Alfred-Workflow - Dash Alfred Workflow