How to run lua script after a plugin loads

[georgev93]

I'm trying to configure a plugin (overseer), where I want to specify opts. I'm doing it the "Lazy.nvim" way by entering the opts into the opts element of the table I'm passing to Lazy.nvim to set up this plugin.

However, here's the catch. I want to run some lua script after the plugin is set up. I would think I could just utilize the config element of this table, but it doesn't look so simple. I'm guessing because of lazy loading? If I uncomment the section of code at the end of this script, the overseer plugin is either loaded with the default opts instead of my opts, or it is interrupted during the setup. I'm not really sure how to tell which. But if I run those commented out lines manually with :lua ... as a command, everything works as expected. So the commented out lines of code are not a problem.

Is there some sort of callback I can use to run some lua script when the plugin finishes loading?

-- ~/.config/nvim/lua/plugins/overseer.lua
return {
  'stevearc/overseer.nvim',
  opts = {
    dap = true,
    templates = {
      'builtin',
      'user.meson_c_build_test',
      'user.meson_c_test',
      'user.meson_c_test_focus',
    },
    log = {
      {
        type = 'echo',
        level = vim.log.levels.WARN,
      },
      {
        type = 'file',
        filename = 'overseer.log',
        level = vim.log.levels.WARN,
      },
    },
    preload_components = {
      'test_cursor.test_cursor',
    },
    component_aliases = {
      -- Most tasks are initialized with the default components
      default = {
        { 'display_duration', detail_level = 2 },
        'on_exit_set_status',
        {
          'on_complete_dispose',
          statuses = { 'SUCCESS' },
        },
      },
      -- Tasks from tasks.json use these components
      default_vscode = {
        'default',
        'on_result_diagnostics',
        {
          'open_output',
          direction = 'float',
          on_complete = 'failure',
          -- on_result = 'if_diagnostics',
          on_start = 'never',
          focus = true,
        },
      },
    },
  },
  keys = {
    {
      '<leader>j',
      function()
        require('overseer').run_template({ name = 'meson_c_test' })
      end,
      mode = { 'n', 'v' },
      desc = 'Run Test',
    },
    {
      '<leader>J',
      function()
        vim.cmd('OverseerQuickAction open float')
      end,
      mode = { 'n', 'v' },
      desc = 'Display previous results in a floating window',
    },
  },
  config = function(_, opts)
    require('overseer').setup(opts)
    -- require('overseer.template').list(
    --   { tags = { 'BUILD' }, dir = '.' },
    --   function(out)
    --     BuildTasks = out
    --   end
    -- )
    -- require('overseer.template').list(
    --   { tags = { 'TEST' }, dir = '.' },
    --   function(out)
    --     TestTasks = out
    --   end
    -- )
  end,
}

[JulianNymark]

I've recently learned about :Lazy profile, it hasn't helped me fully understand how lazy works yet, but maybe there's something you can glean from it 🤔.

(disclosure: I'm a complete newbie to Lazy myself, and I'm on a journey of trying to figure out how the order of plugins & config() works. I also have a plugin that when I run the config() manually after startup is fine, but in the lazy config it isn't)