I somehow have a project that actually has neo vim v0.11.2 on it and I don’t know how. Every other app when I go to install neo vim it forcefully installs v0.5.0 (which doesn’t work at all with my configs or anything). Does anyone know why this is?
Have you used the shell to check the package/ dependency? I’m fairly sure you can remove the package version you don’t want and swap it with the one you want.
Use the shell like your terminal or console. Check the package for the repl / app by running the command.
Uninstall the package completely (clean uninstall)
Then do a clean install of the version you want.
Does this help?
Or, are you just generally asking why it chose one package version over the other?
Actually the dependencies tab doesn’t even appear for me
Okay, so before I give you a list of small tasks for a manual clean un install and re install using the shell.
I want to make sure I’m understanding the question correctly.
Are you asking why the dependencies aren’t showing correctly in general?
Do you want to know how to remove a package that’s not the right version and the normal place to do this is gone?
Or are you saying it generally it does this?
Whenever I make a new app and install neo vim, it automatically installs v0.5.0. If I could use apt then I wouldn’t have this problem, unfortunately i’m stuck with nix. Nix seems to be the problem and isn’t letting me install the correct version. Hopefully that answers your questions
Lol questions about questions boi oh boi lol
I think this usually comes down to the two projects using different nixpkgs snapshots.
In Nix, the version you get isn’t really controlled by the install command it’s controlled by the snapshot your environment is pinned to. So if one project was created at a different time or has a slightly different replit.nix, it might be pulling from a newer nixpkgs revision that includes Neovim 0.11.x, while the others are stuck on an older one that only has 0.5.0.
I’d compare the replit.nix files (and any nixpkgs imports) between the working project and the ones that aren’t. If you make them match, the Neovim version should line up too.
Also worth checking the .replit file in the working project sometimes Replit templates differ slightly and end up pinning different nix setups depending on when the project was created.
⸻
Sources / Documentation
Nixpkgs overview (packages are tied to a specific Git revision):
Nix manual (flakes and pinned inputs / reproducibility model):
NixOS Wiki — nixpkgs explanation (different revisions = different package versions):
https://nixos.wiki/wiki/Nixpkgs
Replit documentation on Nix environments (replit.nix defines dependencies):
Replit Nix configuration details (environment is declarative and reproducible):
Do *it (not this) in the files/ shell manually
Option 1: Remove Neovim from replit.nix (recommended fix)
Edit replit.nix and remove:
pkgs.neovim
Then restart the environment:
replit restart
Option 2: Reinstall Neovim via nix (current environment)
nix-env -e neovim
nix-env -iA nixpkgs.neovim
Option 3: Temporary install (no system change)
nix-shell -p neovim
Option 4: Verify install
nvim --version
which nvim
nix-env -q | grep neovim
Important note
If your environment is pinned to an older nixpkgs snapshot, reinstalling with nix-env may still give Neovim 0.5.0. In that case, the only real fix is updating the nixpkgs source in replit.nix.