Stats API and VeryLazy

[liouk]

Hi,

I've just realised that any plugins that are loaded upon the VeryLazy event don't count in stats().loaded but in fact their load time is part of stats().startuptime. Is this intentional? I'd expect startuptime to reflect all loaded plugins 🤔

Thanks!

[folke]

that's not correct.

• stats.loaded will always be an up to date count of the amount of plugins that are loaded. Calling it before or after Verylazy, or whenever a new plugin is loaded, will give you the updated number.

• startuptime is the time it took for startup

Are you maybe confused because you have a dashboard that displays the stats.loaed, but that dashboard is shown before all plugins are loaded and as such wrong? You can create an autocmd that listens on LazyVimStarted to update the dashboard with the correct info.

[liouk]

Thanks for the reply :) I do have such an autocmd:

  vim.api.nvim_create_autocmd('User', {
    pattern = 'LazyVimStarted',
    callback = function()
      local stats = require('lazy').stats()
      local ms = (math.floor(stats.startuptime * 100 + 0.5) / 100)
      plugins_stats.val = ' '..stats.count..' plugins (loaded '..stats.loaded..' in '..ms..'ms)'
    end,
  })

And what I observe is:

1. I set one plugin (lualine) to load on VeryLazy
2. on startup, my dashboard shows "loaded 7 in 68.01ms"
3. at the same time, :Lazy shows 8 loaded plugins, and in the Profile section startuptime matches 68.01ms and lualine is shown at the end of the profile list

Based on your explanation, I'd expect to see 8 loaded in my dashboard as well 🤔

[folke]

No, you'd see 7 plugins. LazyVimStarted is triggered right after startup, so before VEryLazy

[liouk]

Ah got it! It wasn't clear to me that VeryLazy is triggered after LazyVimStarted, so that's the source of the original question. Thanks!