vim.pack.add can potentially replace bootstrap code

[drowning-cat]

With NVIM v0.12.0 we can use:

vim.pack.add({
  { src = "https://github.com/folke/lazy.nvim.git", version = "stable" },
})

Instead of:

-- Bootstrap lazy.nvim
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
  local lazyrepo = "https://github.com/folke/lazy.nvim.git"
  local out = vim.fn.system({ "git", "clone", "--filter=blob:none", "--branch=stable", lazyrepo, lazypath })
  if vim.v.shell_error ~= 0 then
    vim.api.nvim_echo({
      { "Failed to clone lazy.nvim:\n", "ErrorMsg" },
      { out, "WarningMsg" },
      { "\nPress any key to exit..." },
    }, true, {})
    vim.fn.getchar()
    os.exit(1)
  end
end
vim.opt.rtp:prepend(lazypath)

Warning

Don't expect everything to work.
May require Updating (U) plugins for other :Lazy features to work, such as revert (r) or git log (gl).

Note

Optional

require("lazy").setup({
  root = vim.fn.stdpath("data") .. "/site/pack/core/opt",
  spec = {
    -- Plugins
  },
})

[dpetka2001]

lazy.nvim is not able to manage itself now.

If you do gl to get the git log and try to press r on a commit SHA to revert to a commit, you get an error.

The same way if you have the following plugin spec for Lazy itself

{
  "folke/lazy.nvim",
  commit = "something",
}

It also won't work.

In my personal opinion this kinda defeats the purpose of Lazy itself. People should just use one or the other. Doesn't make sense to configure 2 plugin managers in the user's configuration.

[drowning-cat]

I mean, of course there will be issues — it's an experimental feature in the latest Neovim development version used with the currently unmaintained plugin.

[drowning-cat]

Try updating (U) the plugins to generate lazy-lock.json. Does that make any difference?

[dpetka2001]

No it doesn't matter. Since lazy.nvim will be managed by vim.pack it's not able to manage itself (at least not in the current state, maybe Folke will know better and fix this). So you can't revert back to previous commits via the Lazy UI. Other plugins work fine. It's just lazy.nvim itself that causes problems when you try to manage it via Lazy UI.

And like I said, it's my personal opinion that it doesn't really make sense to use 2 plugin managers just to get rid of the bootstrap code. Each person should just use whatever he wants.

I'm sure there will be a place for both lazy.nvim and the new builtin plugin manager. People who want to go simplistic/minimal will ise the builtin. People who want to retain control of lazy-loading will use Lazy.

Also distros will likely use Lazy, because it can merge different plugin fragments (from different files) into the final spec. I don't know if the builtin can do that yet.

[drowning-cat]

You're right, lazy.nvim itself doesn't work for me either. Sorry, I missed the point.

[dpetka2001]

Yes, it doesn't work because it's not installed in the default root directory. vim.pack uses a different directory where it installs plugins. So, Lazy can't manage itself, because it doesn't see a lazy.nvim directory in ~/.local/share/nvim/lazy/lazy.nvim directory where it would normally look for.