Back to lazy.nvim
Read OriginalThe article details a developer's experience switching from the lazy.nvim package manager to rocks.nvim for Neovim, and then back again. It cites issues with bugs, slow update speeds, and problems running specific tests in rocks.nvim as key reasons for the return. The author highlights that lazy.nvim's recent update added support for luarocks dependencies, removing the primary advantage they saw in rocks.nvim.
0 comments
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
4
Wagon’s algorithm in Python
John D. Cook
•
1 votes
5
An example conversation with Claude Code
Dumm Zeuch
•
1 votes