Where Does Nimble Store Packages?
Nimble installs packages under ~/.nimble, with choosenim toolchains beside it in ~/.choosenim.
Last updated
Nimble, Nim's package manager, installs everything under ~/.nimble in home: package sources in pkgs2 and built binaries linked into bin. Its own settings live separately in ~/.config/nimble/nimble.ini, where nimbleDir can relocate the package tree.
Compilers are the neighbor, not the roommate. choosenim manages Nim versions under ~/.choosenim/toolchains, switching the active one on demand. Back up project lockfiles rather than either folder, since both rebuild cleanly from nimble install.
Where Nimble stores this, by platform
~/.nimble/ (packages) and ~/.choosenim/ (toolchains)
nimble install fills ~/.nimble with pkgs and bin. choosenim manages ~/.choosenim tool versions. Both respect HOME, so custom home layouts move them together. Rebuild from lockfiles instead of copying.
~/.nimble/ (packages) and ~/.choosenim/ (toolchains)
Same layout as Linux. Ensure ~/.nimble/bin precedes system paths or the wrong nimble answers. Xcode command line tools must exist for builds to link.
%USERPROFILE%\.nimble\ (packages) and .choosenim\ (toolchains)
Same split in the user profile. Prefer the choosenim installer over manual zips so PATH entries land correctly. Rebuild environments from lockfiles after machine moves.
Frequently asked questions
nimble installed a tool but the command is missing. Why?
Its bin directory is not on PATH. Add ~/.nimble/bin (or the Windows equivalent) to PATH and reopen the shell. choosenim shims live separately, so check both when commands vanish after a version switch.
How do I reproduce a Nim environment elsewhere?
Commit the .nimble lockfile and rebuild with nimble install on the new machine. Copying ~/.nimble works but drags stale builds along. Pick the toolchain version with choosenim to match.
Notice an outdated path? Let us know.