Using lazy for dependencies but not plugin

[znd4]

My filetype.lua configuration relies on nvim-lua/plenary.nvim. As such, I'd kind of like to do something like

return {
    dependencies = {"nvim-lua/plenary.nvim"},
    config = function()
        require("plenary.path")...
    end,
}

So that it'll always have plenary available when it gets run.

But that isn't a valid plugin spec. I can

return {
    "nvim-lua/plenary.nvim",
    config = function()
        require("plenary.path")...
    end,
}

But I'm not sure if I can use the same plugin times.

This might be abusing lazy.nvim, but I'm curious what patterns others use / have found for this.

EDIT: I guess I could use dir + split my code into a separate repo, but that feels like a lot more complexity than is warranted

[DRKolev-code]

I second this. I like the idea of separating plugins into opts/keys. I have the same for my custom scripts. I would like to be able to do:

return {
    setup/custom/plugin/type = <value to indicate to not search for setup>,
    dependencies  = {nui}, -- optional
    opts = require("mine/opts/terminal"), -- optional
    keys = require("mine/keys/terminal"), -- optional
    config = function(_, opts) ... end, --optional if we provided opts
}

Maybe if there is a switch: setup = nil, custom = True or plugin = False or type = custom/plugin or anything like that.

Or maybe just the absence of any url, dir should be enough.

Then config to be loaded based on the available loading mechanisms of Lazy.