Initialize plugin only after build is complete

[vyfor]

Hello,

My plugin uses Rust for the backend and does that by loading the compiled dynamic library with LuaJIT's FFI module. So the library needs to be built before the plugin is loaded, or otherwise it will lead to an error. With the configuration below, lazy attempts to call setup before the plugin is built. This may be the default behavior, but is there a way to have it the other way around?

Thanks!

{
  'vyfor/cord.nvim',
  event = 'VeryLazy',
  build = './build',
  opts = {},
}

[vyfor]

Maybe I should turn this into an issue.

[Shougo]

OK. It works for me.

So it is not lazy.nvim issue.

require('lazy').setup({
  {
    'vyfor/cord.nvim',
    build = './build',
    opts = {},
    config = function()
      require('cord').setup {
        usercmds = true,                              -- Enable user commands
        log_level = 'error',                          -- One of 'trace', 'debug', 'info', 'warn', 'error', 'off'
      }
    end,
  },
}, {})

[vyfor]

@Shougo Well, in my case it certainly loads the plugin before running the build. Can you try doing a fresh install, e.g. rm -rf ~/.local/share/nvim/lazy/cord.nvim, then start nvim and see the message logs?

[Shougo]

Error detected while processing /home/shougo/work/test/test_lazy.lua:
[cord.nvim] Could not find the compiled dynamic library at: /home/shougo/.local/share/nvim/lazy/cord.nvim/cord.so. Please re-run the build script

Hm... after installed the message is displayed.
But if I restart neovim, the error message is gone.

[vyfor]

Yeah, since the library will already be built on subsequent launches.

[vyfor]

As of now, users are forced to restart neovim to be able to use the plugin.

[folke]

I'd rather not make that configurable.

I just changed it to only load the plugin when using a build command as :....

See 5bdb12a

[vyfor]

That works, thanks!