A community repository of common plugin specifications https://astronvim.github.io/astrocommunity/
Find a file
boydaihungst 5c9c55c0f2
fix(markdown-preview-nvim): Change build command to download prebuilt version of markdown-preview. (#1640)
Co-authored-by: Uzair Aftab <48220549+Uzaaft@users.noreply.github.com>
2025-09-15 13:13:03 +02:00
.github ci: trigger actions only in original repository (#1418) 2025-04-03 09:47:47 -04:00
docs fix(docs): use correct favicon (#1394) 2025-03-19 23:24:36 -04:00
lua/astrocommunity fix(markdown-preview-nvim): Change build command to download prebuilt version of markdown-preview. (#1640) 2025-09-15 13:13:03 +02:00
.gitignore build: add in nix devShell, and ignore direnv (#1407) 2025-04-03 09:53:10 -04:00
.luarc.json chore: configure lua language server to disable formatting 2025-06-06 08:17:41 -04:00
.neoconf.json fix: disable lua_ls formatting with Neoconf 2023-07-06 09:16:50 -04:00
.stylua.toml feat(themes): add catppuccin 2023-02-21 10:03:31 -05:00
CHANGELOG.md chore(main): release 19.0.0 (#1471) 2025-05-21 09:53:19 +02:00
CONTRIBUTING.md docs(main): make discord link permanent (#990) 2024-05-24 14:57:55 -04:00
flake.lock build: add in nix devShell, and ignore direnv (#1407) 2025-04-03 09:53:10 -04:00
flake.nix build: add in nix devShell, and ignore direnv (#1407) 2025-04-03 09:53:10 -04:00
LICENSE Initial commit 2023-02-21 09:55:57 -05:00
neovim.yml Merge branch 'main' into v4 2024-03-20 19:26:30 +01:00
README.md docs(main): Remove badges (#1454) 2025-04-18 08:02:12 -04:00
selene.toml chore: move to selene for linting 2024-03-01 10:08:11 -05:00

AstroNvim Community Repository

AstroNvim's community repository contains plugin configuration specifications — a collection of plugins contributed by the community for AstroNvim, a NeoVim configuration. These specifications help manage the variety of plugins used in AstroNvim.

📦 Setup

To integrate the community plugins, add the provided configurations to your plugins setup preferably before you import your own plugins to guarantee all AstroCommunity changes are loaded before your own overrides. If you are using the AstroNvim Template This can be done in your lua/community.lua file. If you're unfamiliar with configuring plugins, we recommend referring to the AstroNvim documentation.

Importing AstroCommunity Plugins

Integrate the following content within your lua/community.lua file:

return {
  "AstroNvim/astrocommunity",
  { import = "astrocommunity.colorscheme.catppuccin" },
  -- ... import any community contributed plugins here
}

Customizing AstroCommunity Installations

Once you have AstroCommunity imports defined in your lua/community.lua you can then further customize the installations in your own plugin definitions (typically done in the lua/plugins/ directory). Here is an example assuming you have Catppuccin installed as shown above.

return {
  { -- further customize the options set by the community
    "catppuccin",
    opts = {
      integrations = {
        sandwich = false,
        noice = true,
        mini = true,
        leap = true,
        markdown = true,
        neotest = true,
        cmp = true,
        overseer = true,
        lsp_trouble = true,
        rainbow_delimiters = true,
      },
    },
  },
}

Notes:

  • To disable imports, set the enabled option to false. You have two approaches to modify an existing plugin: use the full repository name (e.g., "m4xshen/smartcolumn.nvim") or the module name (e.g., "catppuccin"). Remember, the module name might differ from the folder name.
  • It's recommended to use the full import path when customizing a plugin, and not the shorthand notation of just the repository name.
  • You can override many aspects of community plugins including settings, dependencies, and versions. For more details on available options, refer to the lazy.nvim documentation.

Contributing

If you've written a plugin configuration and wish to add it with the AstroCommunity repository, please follow our Contribution Guidelines and submit a pull request. Ensure you've rigorously tested your changes before submission. This isn't an official repository, so its stability relies on community contributions. We're excited to see how this project grows and evolves!