ref here
Hi,
I briefly checked the code and noticed that cmake-tools.nvim is using several modules from plenary.nvim:
plenary.path
plenary.scandir
plenary.job
plenary.popup
Plenary.nvim is going to be archived soon (maintenance will likely stop around June 2026, and many plugins have already started removing their dependency on it).
Neovim now provides strong built-in alternatives:
plenary.path → vim.fs + vim.uv (e.g. vim.fs.normalize, vim.fs.joinpath, vim.fs.dirname, vim.fs.find, vim.uv.fs_stat)
plenary.scandir → vim.fs.dir() or vim.fs.find()
plenary.job → vim.system() (available since Neovim 0.10, much cleaner and officially recommended)
plenary.popup → MunifTanjim/nui.nvim (nui.popup)
Many popular plugins (gitsigns, telescope, etc.) have already migrated or are in the process of doing so to reduce external dependencies and improve long-term maintainability.
Would you consider gradually migrating these modules to the built-in Neovim APIs and lightweight alternatives? This would help make cmake-tools.nvim more future-proof and remove the hard dependency on plenary.nvim.
I'm happy to help test or even contribute some of the migration patches if needed.
Thanks for maintaining this great CMake integration plugin!
ref here
Hi,
I briefly checked the code and noticed that cmake-tools.nvim is using several modules from
plenary.nvim:plenary.pathplenary.scandirplenary.jobplenary.popupPlenary.nvim is going to be archived soon (maintenance will likely stop around June 2026, and many plugins have already started removing their dependency on it).
Neovim now provides strong built-in alternatives:
plenary.path→vim.fs+vim.uv(e.g.vim.fs.normalize,vim.fs.joinpath,vim.fs.dirname,vim.fs.find,vim.uv.fs_stat)plenary.scandir→vim.fs.dir()orvim.fs.find()plenary.job→vim.system()(available since Neovim 0.10, much cleaner and officially recommended)plenary.popup→MunifTanjim/nui.nvim(nui.popup)Many popular plugins (gitsigns, telescope, etc.) have already migrated or are in the process of doing so to reduce external dependencies and improve long-term maintainability.
Would you consider gradually migrating these modules to the built-in Neovim APIs and lightweight alternatives? This would help make cmake-tools.nvim more future-proof and remove the hard dependency on plenary.nvim.
I'm happy to help test or even contribute some of the migration patches if needed.
Thanks for maintaining this great CMake integration plugin!