download plugin via http, not git

[v-georg-v]

Hello!
I have a closed corporate network at work. I and many people can't download plugins with current functionality of lazy.nvim. Downloading them manually and placing them in the appropriate directory is a good option, but when there are more than 50 plugins and they need to be updated, a little automation—a script that downloads and saves—is a lifesaver.

Question: Do you have any plans to develop functionality for downloading via http with lazy.nvim.
if not, is it possible to implement function which will give me all plugins and dependencies. I reed code and docs. I can get plugins, but I don't figure, how to get dependencies of plugin. with this function, I can make my custom plugin to download via corporate http proxy

[UxaS]

Hi, I have a similar situation: access to github.com is blocked for git clone. And downloading archives from github is prohibited. There is a corporate repository from which you can download plugins. Moreover, the plugins in the repository are stored as zip files. Is it possible to extend the functionality of lazy.nvim so that its configuration allows specifying the corporate repository URL and forbids downloading plugins from github?

In short, the goal is to transparently download plugins in zip format from the corporate repository as if the plugins were hosted on github

[rootex-]

Hi all!
Same story here, git clone is not available via corporate proxy.
At the same time, using curl to download something from external resources is immediately detected by DLP systems.
But you can still get plugins using URLs like https://proxy_for_github/path/to/plugin with releases and tags options or smth like master.zip.
It's quite tedious to maintain two configs for corp and home environments.

[nikolay-grudanov]

Hello!

I’m facing the same issue in my corporate environment. Direct git access is blocked by network policies, which makes the current plugin installation workflow with lazy.nvim impossible.
The ability to download plugins via HTTP/HTTPS (either as archives or through a corporate proxy) would be extremely valuable for many developers working in restricted network environments. This feature would enable:

• Downloading plugins as zip/tar archives from GitHub releases or custom URLs
• Using corporate proxy servers for plugin distribution
• Maintaining a single configuration that works across both restricted and open network environments

I understand this adds complexity to the plugin manager, but even a basic API or hook system that exposes plugin dependencies would allow us to implement custom download logic while keeping lazy.nvim’s excellent dependency resolution and management features.
Would you consider adding support for alternative download methods (HTTP archives, custom URLs) or at least exposing an interface to retrieve the full dependency tree programmatically?

Thank you for maintaining such a great tool!