-
-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lockfile support #731
Comments
Update: I'm working on this atm. The plan is to mimic lazy.nvim's lockfile mechanism so that it is somewhat familiar to users. I'll cut the |
Update: I'm still working on this and have a feature branch locally which I'm not too happy with yet. I think I'll try to get a first implementation merged soon and make it opt-in and tag it as experimental and gather user feedback in order to guide additional features and shortfalls. |
Any updates on this? This would be such a helpful feature to keep track of things and ensuring your dev environment works as intended across machines, thanks for your hard work on mason ❤️ |
I have implemented a lockfile mechanism that works for my use case, hopefully this is to some help for people waiting here https://github.com/zapling/mason-lock.nvim |
I'd love to be able to commit a Mason lockfile alongside my nvim config so that when I move to a different computer Mason can automatically install everything I installed on the other machine, with matching versions. Jumping between my work and personal laptop, I keep forgetting to install one thing or another. Installing is a breeze with Mason, though! |
I've searched open issues for similar requests
Yes
Is your feature request related to a problem? Please describe.
Sometimes formatters change how they work and updating them results in an unnecessary diff.
Describe the solution you'd like
It would be great to add a function to generate a lockfile that will describe installed packages with their version.
Packer is already working on supporting this.
This feature would add more stability to one's neovim configuration and less worry that something will break if you reinstall your OS or install neovim on a different machine.
Describe potential alternatives you've considered
Specifying each package manually is a tedious work. Besides, I use null-ls plugin that automatically detects what needs to be installed.
"Just don't update" won't work, because I need the versions persist on any computer I am working on.
Additional context
No response
The text was updated successfully, but these errors were encountered: