Open jaredmontoya opened 7 months ago
It seems like this is because of the way luarocks.nvim sets the package.path. It only looks for a <plugin>.lua
file instead of a <plugin>/init.lua
file in addition. Should be quite a simple fix - I'll be making a PR soon :)
this issue should be fixed in #5
Thank you for solving this issue as this is basically the only thing that stands between people who use lazy.nvim and them using neovim plugins that require luarocks.
I think it has something to do with dbus_proxy entrypoint structure(it's a directory) but I don't think the rock is broken, maybe it relies on some deprecated import behaviour. I can't say for sure because I am not a lua developer.
moving init.lua out of dbus_proxy directory at
~/.local/share/nvim/lazy/luarocks/.rocks/share/lua/5.1
and renaming it to dbus_proxy.lua made it available