Replies: 1 comment 2 replies
|
Hey 👋 I'm not sure I understand this. rocks.nvim takes care of managing dependencies for you. In your example, telescope_fzf_native and telescope_ui_select are extensions, not dependencies. rocks-git.nvim currently doesn't support managing dependencies, and when it does, it will only be possible if the plugin has a rockspec in its repository root. If you need to configure plugins and their extensions together, take a look at rocks-config.nvim and its plugin bundles. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
In general, how can I determine the dependencies of a package, most of the prerequisites are due to my configuration type, which are prerequisites of another package, and in the default state, they may not be prerequisites of that package, this confused me a little.
I am going to fully transfer nvpak from lazy.nvim to Rocks.nvim and this is a need to be able to manage dependencies.
All reactions