paq-nvim VS lit

If you want a dead simple package mamage that only puts packages in opt and start, you can use paq.nvim

Is there anyone here who can share some feedback on how much lazy.nvim has been better than what you were using previously? If my context helps, I'm using paq-nvim, previously was using packer.

This was a problem when I was using paq as my manager, now I have the same problem with packer. It never happened when I wanted to install new plugins, only on updating. With packer I have a workaround: after it fails to sync it allows to re-run all failed jobs, and each times about a half of failed jobs fail again, others update successfully, so I can iteratively sync everything, but that's a terrible waste of time;

Options: - packloadall command family and maybe git submodules - minpac which is a thin utility around the above - vim-plug - old but still popular for it does the job - packer.nvim is a popular choice for lua configs, never got to using it myself - paq-nvim is another often mentioned lua solution - dozens of other solutions

that sounds like paq, but slow?

On my Neovim setup, I simply have the following plugins. I use paq as a plugin manager:

paq.nvim

Another project that uses git as a storage medium is a package server for the node.js API implemented in Lua: https://github.com/luvit/lit.

Both serve files from a git repository, and lit will actually write to the repository.

Hello would it be possible to use proxies with the luvit/coro-http api? https://github.com/luvit/lit https://bilal2453.github.io/coro-docs/docs/coro-http.html It doesn't seem to be anywhere and I really need this.