refactor(main): Replace `echasnovski` with `nvim-mini`
@mehalter need a review from you. Blocked on Astronvim/astronvim#2822
Review Checklist
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
-
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex.
feat(utility): added noice.nvim plugin -
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex.
fix(noice-nvim): fix LSP handler error -
[ ] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
-
[ ]
READMEis properly formatted and uses fenced in links with<url>unless they are inside a[title](url) -
[ ] Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).
-
[ ] Proper usage of
optstable rather than setting things up with theconfigfunction. -
[ ] Proper usage of
specstable for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).
This shouldn't happen until AstroNvim v6