mason-registry
mason.nvim
mason-registry | mason.nvim | |
---|---|---|
5 | 108 | |
125 | 6,871 | |
8.8% | - | |
10.0 | 7.7 | |
4 days ago | 7 days ago | |
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.
mason-registry
-
Show HN: Postgres Language Server
Can you try to get it added to Mason so people don't have to try and do a custom install?
https://github.com/mason-org/mason-registry/
- saltstack development in neovim
-
Astronvim Python DAP not starting
There was a bug in the new mason registry that I fixed this morning: https://github.com/mason-org/mason-registry/pull/1056
-
PSA: Changes to the mason.nvim registry
Hello! This is a PSA for people who use mason.nvim (tl;dr at the bottom). Going forward the core registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This decouples the infrastructure in such a way that the Lua plugin becomes a standalone client that can be hooked into more registries than just the core one, as well as more easily be subject to versioning (mason.nvim currently doesn't version itself due to the fact that packages are bundled with it, which complicates things). This decoupling also lowers the barrier of entry for additional maintainers who can solely focus on the registry, without having to learn the internals of the plugin (more info will come soon if you're interested in possibly helping maintain the core registry).
Going forward the core mason.nvim package registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This will be a fully seamless migration so you shouldn't notice anything and there is no action required. Refer to the full announcement post for more information.
mason.nvim
- I can't stand using VSCode so I wrote my own (it wasn't easy)
-
Using a venv with Neovim's Python LSP
I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
-
Do I need a plugin manager ?
I'm using mason.nvim to install my dependencies, I've this snippet at nvim/plugin/mason.lua so after cloning my dotfiles I can just run:
-
Mason can't install gopls (or gofumpt, or goimports)
The suggestion from this thread fixed it for me. I just needed to unset GOOS and GOARCH then restart neovim.
-
Neovim documentation is pretty bad
For instance, I'm trying to install rust-analyzer in lazyvim from https://github.com/williamboman/mason.nvim. The installation instructions are:
- LazyVim
-
How do you enable semantic highlighting for Python?
I have pyright installed via mason which apparently support "semantic token highlighting" but have been having a hard time getting these colors to show up in a buffer. It seems Neovim has changed how it handles semantic highlighting a few times so there's still some conflicting information online. It's hard to know what's current and what's not. Any help would be greatly appreciated.
-
language server not installed or missing from path
Use mason to install the language servers you want.
-
Why is nobody using CoC anymore?
Because null-ls.nvim & mason.nvim together do everything I wanted CoC for
What are some alternatives?
atlas - Manage your database schema as code
lazy-lsp.nvim - Neovim plugin to auto install LSP servers
declarative-schemas
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nil - NIx Language server, an incremental analysis assistant for writing in Nix.
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
purl-spec - A minimal specification for purl aka. a package "mostly universal" URL, join the discussion at https://gitter.im/package-url/Lobby
omnisharp-vim - Vim omnicompletion (intellisense) and more for C#
language-server-protocol - Defines a common protocol for language servers.
formatter.nvim
vscode-postgres - PostgreSQL extension for vscode providing explorer, highlighting, diagnostics, and intellisense
neoformat - :sparkles: A (Neo)vim plugin for formatting code.