feature: Install to lockfile when missing

[EdenEast]

Did you check docs the docs?

• I have read all the lazy docs

Is your feature request related to a problem? Please describe.

install.missing is great and keeps my config from breaking saying that a plugin is missing and not installed. However when it checks missing it calls the install. Install does not take the lockfile into account.

lazy.nvim/lua/lazy/core/loader.lua

Lines 33 to 42 in c1f39f9

	if Config.options.install.missing then
	Util.track("install")
	for _, plugin in pairs(Config.plugins) do
	if not plugin._.installed then
	for _, colorscheme in ipairs(Config.options.install.colorscheme) do
	if pcall(vim.cmd.colorscheme, colorscheme) then
	break
	end
	end
	require("lazy.manage").install({ wait = true })

The result is that the plugin will be installed at the latest commit. Also now that install calls update on the lockfile then lockfile will be updated with the latest change.

Describe the solution you'd like

Having an option to tell install that I would like to install to the the commit specified in the lockfile if it exists.

Describe alternatives you've considered

I tried to set install.missing = false and then call restore manually but when launching nvim it fails loading my config saying that everything does not exist.

Additional context

No response

[folke]

This is a very specific use-case. What you can do:

• let lazy install everything
• revert the lockfile to what you had in git
• run lazy restore

[EdenEast]

I disagree, and would argue that this is the default case. As there is a lockfile I would expect that the version that is specified in the lock file would be set when doing operations like installing.

[folke]

After thinking about it more, you are right.

I just pushed an update so that missing plugins will always be installed with the existing commit in the lockfile.

[atinylittleshell]

@folke it looks like the behavior regressed. Whenever lazy auto installs a missing plugin it would install the latest commit and change the lockfile instead of respecting it. This kind of defeats the purpose of the lockfile IMO.

I have multiple devices and environments that share the same dot files, and I generally don't want to update my plugins (to avoid dealing with breaking changes when I just need my editor to work). This behavior would basically keep updating my plugins whenever I start nvim on a device that hasn't got some of the plugins yet - quite an inconvenience to deal with..