Skip to content

alex-popov-tech/store.nvim

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

53 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

store.nvim heading image store.nvim ui

Features

A Neovim plugin for browsing and installing Neovim plugins through an intuitive UI interface.

  • ๐Ÿคฏ Plugins installation: Easily install plugins with lazy.nvim without leaving terminal
  • ๐Ÿ’… Live README Preview: Real-time markdown rendering with syntax highlighting
  • ๐Ÿค“ Smart Filtering and Sorting: Filter/sort plugins name, tags, author, activity and so on
  • ๐Ÿงณ Efficient Caching: configurable 24-hour 2-layer cache with automatic staleness detection and manual refresh

Installation

Using lazy.nvim

{
  "alex-popov-tech/store.nvim",
  dependencies = { "OXY2DEV/markview.nvim" },
  cmd = "Store",
  keys = {
    { "<leader>s", function() require("store").open() end, desc = "Open store.nvim modal" }
  }
}

Usage

Open the plugin browser with :Store or require("store").open(), and follow hints from help window.

โ“ FAQ

Why is plugin not listed?

That usually happens in two cases:

  • Repository doesn't have the neovim-plugin or neovim-plugins tag
  • Those tags were added less than 24h ago, and the crawler hasn't refreshed the database yet

If neither applies โ€” please create an issue.

Why is plugin not installable?

A plugin is considered installable if it has at least one valid configuration block in its readme. If it isnโ€™t marked as installable, try the following:

  • Wait up to 24h after last readme change โ€” the crawler needs time to re-fetch and re-process it.
  • Make sure code blocks contain valid Lua code. You can check this using lua-ls โ€” just create a tmp.lua file and paste the code block into it.
  • Adding clear context before code blocks helps too. For example, prefix it with something like: lazy.nvim configuration example.
  • You can also check the latest debug artifacts from the README processor here.

If none of that helps, and your plugin should be installable โ€” please create an issue.

I have a lazy.nvim config in readme, but store.nvim suggests using a migrated version from packer/vim-plug.

By default, native lazy.nvim configs are preferred. If you have one but it's not being used:

  • Wait up to 24h after your last README.md change โ€” the crawler may not have picked it up yet.
  • Ensure your lazy.nvim config block is valid Lua. lua-ls can help with that (try pasting it into a temporary tmp.lua file).

Still not working? Please create an issue.

About

Not a plugin manager, but plugin magazine ๐Ÿ’…

Topics

Resources

License

Stars

Watchers

Forks

Contributors 3

  •  
  •  
  •  

Languages