I wanted to let you all know that the mini.nvim plugin collection has been moved from the original author’s personal GitHub account to a new dedicated organization called nvim-mini.
What This Means for Users
First off, don’t worry - the original developer isn’t abandoning the project. This move is actually meant to make mini.nvim more stable in the long run. A few trusted contributors have joined the team to help maintain everything.
Do You Need to Update Your Config?
The old GitHub links should still work and redirect automatically, but it’s better to update your plugin manager setup to use the new organization. Here’s how:
For mini.deps users:
-- Old way
add('echasnovski/mini.nvim')
-- New way
add('nvim-mini/mini.nvim')
For lazy.nvim users:
-- Update your plugin spec
{
'nvim-mini/mini.nvim',
config = function()
require('mini.starter').setup()
end
}
After changing your config, restart Neovim and run your plugin manager’s sync command.
Why the Move?
The main reasons include getting more people involved in development, creating space for future Neovim projects, and potentially setting up proper funding for the project.
The project is also getting a slight rebrand to MINI (Modular Independent Neovim Improvements) to better reflect its scope.
Sorry for any inconvenience this might cause. The goal is to make everything more reliable going forward!
just updated mine - everything’s working smoothly. anyone know if the old echasnovski repo will stay up forever, or is there a timeline for when the redirects might break? this thread should probably be pinned since mini is pretty popular here.
Perfect timing on this announcement. I switched to the new organization URLs yesterday after my package manager started acting weird with updates. The transition was seamless once I updated the repo paths in my config. If you’re on the fence about switching, do it now. Long-term redirects suck for plugin management. Also love that they’re adding more maintainers - having one person control such a popular plugin collection always made me nervous.
Good to see the project getting more organizational backing. I’ve been using mini.nvim modules for six months now and they’re essential to my workflow. Updated my lazy.nvim config to point to nvim-mini and everything pulled down fine. If you use custom forks or local modifications, double check those references - some might still point to the old echasnovski paths. The MINI rebrand makes sense given how much the plugin collection has grown.
Nice move on the better organization! I ran into this exact thing last month - one of our key dependencies switched repos and killed our CI pipeline.
I got tired of manually tracking plugin updates across the team, so I built automated monitoring with Latenode. Simple workflow that watches for repo changes and updates our dotfiles with new URLs. Shoots us Slack alerts when plugins move or get deprecated.
You can take it further - monitor release notes and auto-test config changes in sandbox before pushing to main. No more broken setups during team meetings.
If you’re managing multiple Neovim configs or working with a team, automation like this prevents major headaches. Plugin ecosystems move fast and manual tracking doesn’t work.