packspec
lazy.nvim
packspec | lazy.nvim | |
---|---|---|
7 | 131 | |
205 | 11,729 | |
2.0% | - | |
4.8 | 9.3 | |
3 months ago | 11 days ago | |
Lua | Lua | |
Apache License 2.0 | Apache License 2.0 |
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.
packspec
- This Week In Neovim #31 – Mon Feb 13 2023
-
Introducing Luarocks-Tag-Release - Publish your Neovim plugins to LuaRocks
It looks like there's a WIP package specification that might also support source = luarocks://.
-
Standardizing Neovim package management API - could or should this be a thing? Let’s talk about it!
I was hoping you would clarify exactly what you're proposing so I could forward the appropriate link, otherwise I'm just guess based off a vague (but long) post. Based on other replies in this reddit post, I'm not the only one confused by your ambiguous and likely incorrect terminology. It sounds like you're looking for a specification, which exists https://github.com/nvim-lua/nvim-package-specification, it just isn't well adopted. There's also countless Github issues and discussions about this on IRC which you could find by a simple Google search. It really just depends on what you're alluding to which is why I linked what an API was so you could be more specific. If you're looking for the plugin managers API (notice the qualifier) to be consistent, then that's not a good idea since the API of the plugin manager is what differentiates them, it's like saying all programming languages should be the same, the only thing different should be the backend (e.g. gcc vs llvm). The consistency should be at a different layer (thus the plugin spec).
-
Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
packspec, a package specification for neovim to address the dependency issue
-
Opinion on better plugin management?
There is an issue for it: https://github.com/nvim-lua/nvim-package-specification/issues/23
lazy.nvim
-
How to override the colors of NeoSolarized in NeoVim
First, I installed NeoSolarized.nvim via lazy.nvim, so the code would be simple like the following one.
-
Easy Access to Terminal Commands in Neovim using FTerm
In my case, I have switched to Lazy.nvim for all of my Neovim plugin needs ( Thanks again Folke! ), so it would be great if you were at least minimally familiar with how Lazy works as well.
-
Neovim: creating keymaps in lua
If you've read old tutorials about Neovim configuration you've find the way they create keymaps is a little bit different from what people do now. And if you check other people's configuration sometimes you'll find they create their keymaps using lazy.nvim. This is causing confusion among Neovim users.
- Enchula Mi Consola
-
Pimp your CLI
The basic plugins will be downloaded on the first run using Lazy, a package manager for Neovim that loads only the necessary plugins as you use them. Once it's done you should be looking at a full-fledged IDE.
-
It’s been an hour and I have made no progress
it looks more like something is wrong with your neovim install rather than your config. based on this lazy.nvim issue you may have an updated neovim binary but your neovim runtime files are not up to date. try completely reinstalling neovim.
-
Do I need NeoVIM?
It is possible to manage plugins yourself, but I would recommend a plugin manager such as Lazy (https://github.com/folke/lazy.nvim). There are many more plugins that most would argue are virtually essential, but these should at least be able to get you some autocompletion and highlighting without too much messing about. Be sure to read the install instructions for each of these plugins!
-
neorg problem, all other plugins deactivate when added to init.lua
whenever i add this: ``` -- bootstrap lazy.nvim local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath)
-
Ansible-based dotfiles with fancy nvchad-based neovim + tmux setup
Easily updatable. Versions are stored in manifests and can be easily updated with a single command. neovim's lazy-lock.json however is managed separately by lazy.
-
Packages only work when I install a new one
require("keymaps") local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath) require("lazy").setup({ "folke/tokyonight.nvim", {"nvim-treesitter/nvim-treesitter", build = ":TSUpdate"}, { 'nvim-telescope/telescope.nvim', tag = '0.1.4', dependencies = { 'nvim-lua/plenary.nvim' } } })
What are some alternatives?
nvim-conf - ☄ Maddison's Neovim configuration!
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
luarocks - LuaRocks is the package manager for the Lua programming language.
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
vscode-eslint - VSCode extension to integrate eslint into VSCode
kickstart.nvim - A launch point for your personal nvim configuration
lsp-format.nvim - A wrapper around Neovims native LSP formatting.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
neovim - Vim-fork focused on extensibility and usability
LazyVim - Neovim config for the lazy
fabn
nvim-treesitter - Nvim Treesitter configurations and abstraction layer