Why not add a build.lua?

[winstxnhdw]

This way we can avoid the build step.

[f3fora]

at the time, build.lua wasn't a thing.
feel free to open a PR!

[winstxnhdw]

Done.

[f3fora]

I personally think that adding build.lua or any other building script is not worth the effort, since

• build.lua is Lazy.nvim specific.
• the go build ... is a small string which changes a lot depending on the machine and the user preferences, and so a default value is not so useful.
• the code to execute a shell command needs to be implemented and maintained.

Plugins managers already implement solid command execution, which I do not believe it is worth re-implement.
For exemple, the ideal way to execute go build will be via vim.loop.spawn (using cwd option to set the correct folder.) as already done by Lazy.nvim and others.

In the end, the only changes with a build.lua will be the introduction of a build flag in the plugin config and so to have a configuration that looks like this:

{
    'f3fora/nvim-texlabconfig',
    opts = {
        build = 'go build --whatever-flags',
        ...
    },
}

instead of this:

{
    'f3fora/nvim-texlabconfig',
    opts = {
        ...
    },
    build = 'go build --whatever-flags',
}

since I personally use different flags depending on what machine I use.

[winstxnhdw]

Sure, but you're making users do a lot of work just to setup a simple plugin, especially since go build without flags don't work OOTB.

If we use build.lua, they only need to add their Lazy dir to PATH.