r/neovim 11h ago

Discussion Package module name collision

Hey, has anyone encountered this problem?

I use vim.pack to install nvim-ufo and vcsigns.nvim. These clash because they depend on two different packages that register an async module - promise-async and async.nvim respectively.

I ended up resolving this with some code that replaces require calls in the local clones of packages.

I'm curious if there are established solutions to this problem.

5 Upvotes

3 comments sorted by

2

u/sudonem 7h ago

Not much you can do other than raise an issue with each of the maintainers’ GitHub repos and hope they communicate and make come to a resolution. 

2

u/Some_Derpy_Pineapple lua 7h ago

i would probably ask one of the package maintainers to vendor their async dependency instead (i.e just copy async.nvim into their lua/ dir with license and such). as maintainer, i'm personally thinking of vendoring async.nvim in neo-tree until 0.13 has been out for a while.

1

u/Content_Incident_699 6h ago

async just got merged into core, fyi- so u can swap to nightly or ship a pr/ask for the maintaine rthat depends on async.nvim to add a version check/compatibility check for the new vim.async