packspec VS nvim-conf

It looks like there's a WIP package specification that might also support source = luarocks://.

I was hoping you would clarify exactly what you're proposing so I could forward the appropriate link, otherwise I'm just guess based off a vague (but long) post. Based on other replies in this reddit post, I'm not the only one confused by your ambiguous and likely incorrect terminology. It sounds like you're looking for a specification, which exists https://github.com/nvim-lua/nvim-package-specification, it just isn't well adopted. There's also countless Github issues and discussions about this on IRC which you could find by a simple Google search. It really just depends on what you're alluding to which is why I linked what an API was so you could be more specific. If you're looking for the plugin managers API (notice the qualifier) to be consistent, then that's not a good idea since the API of the plugin manager is what differentiates them, it's like saying all programming languages should be the same, the only thing different should be the backend (e.g. gcc vs llvm). The consistency should be at a different layer (thus the plugin spec).

packspec, a package specification for neovim to address the dependency issue

There is an issue for it: https://github.com/nvim-lua/nvim-package-specification/issues/23

My plugin definitions

I keep plugin configurations in my lua/user/plugin/ directory. If the plugin's options are short, I keep them in a file called misc.lua, otherwise I create a separate file with the name of the plugin. Check out my config to see what I mean.

Here is my configuration currently, nearly all Lua. Here is what it looked like when it was still VimScript (quite messy).

Please head over to the README for more examples, or check out my config to see how I actually use Mapx.