How to Search for Neovim Plugins on Dotfyle

Dotfyle is a discovery and sharing site for Neovim plugins and configurations. You can search by plugin name or keyword, filter configurations by plugin manager, plugins, or language servers, and browse trending, popular, and new plugin lists. Plugin detail pages show installation counts and configuration examples so you can judge adoption before installing.

Searching by name or keyword

Use the site's search to look up a plugin by name (for example, telescope or lazy.nvim) or by a broader term like completion or debugging. Results surface both plugins and configurations, so you can move from "does this plugin exist?" to "how are other people wiring it up?" in one step.

Browsing the curated lists

If you don't have a specific plugin in mind, Dotfyle organizes plugins into lists that answer different questions:

The homepage excerpt shows the scale of the data behind these lists: roughly 2,686 plugins, 7,000 developers, and 100,527 plugin installations. Popular entries carry a config count, which is a useful proxy for how many public configurations actually use the plugin — for example, nvim-treesitter/nvim-treesitter shows 2,526 configs, neovim/nvim-lspconfig 2,385, nvim-lua/plenary.nvim 2,306, and folke/lazy.nvim 2,277.

Filtering configurations

Configuration search is the part that distinguishes Dotfyle from a plain plugin index. You can narrow configurations by:

• Plugin manager — e.g. lazy.nvim, packer, vim.pack
• Plugins — find configs that include a specific plugin
• Language servers — find configs set up for a particular LSP

This is useful when you want a working reference rather than a README. If you're setting up a language server and want to see how others structure it, filter by that server and read through the matching init.lua files.

Reading a plugin detail page

A plugin entry typically gives you:

• Installation count — how widely it's used
• Config count — how many public configs reference it
• Tags — categories like syntax, lsp, completion, debugging, plugin-manager, scrollbar
• Configuration examples — links into real configs that use the plugin

New plugins appear with small numbers early on. In the homepage excerpt, for instance, mihovilrak/scroll.nvim (scrollbars plus an optional minimap with git and LSP markers) and JarnDev/autodap.nvim (zero-config debugging over nvim-dap, monorepo-aware for Node/Python/C-C++) both show low install counts — expected for recent additions, and not a signal of quality either way.

Checking configurations directly

The configurations section lists public repos with a path and a config count. Examples from the excerpt include le4ker/nvmegachad (/, init.lua), Rahularya01/neovim-config (/, init.lua), dominionthedev/dotfiles (/nvim, init.lua), and umiyosh/ai-polish.nvim (/lua/ai-polish, init.lua). Opening one shows the full setup, which is often faster than assembling a config from individual plugin READMEs.

Following Neovim news

Dotfyle also publishes This Week in Neovim, a recurring news roundup. Recent issues cover topics such as the most popular plugins published at the end of 2024, NeovimConf and VimConf 2024 playlists, Supermaven code completion, markdown live preview with markview.nvim, and session management with persistence.nvim. You can subscribe by email or follow the RSS feed.

Practical search tips

• Start with a keyword search, then switch to configuration filtering once you know which plugin you want.
• Sort your attention by config count when comparing similar plugins — a high count means more examples to learn from.
• Use the language server filter when your goal is editor setup rather than plugin choice.
• Check the "new" lists periodically; plugins there won't have many configs yet, so read the source or README instead.
• Cross-reference a plugin's tags against your needs (e.g. debugging, completion, plugin-manager) to avoid scanning unrelated results.