Stale package versions persist after editing replit.nix in Replit

Stale package versions persist after editing replit.nix in Replit

The goal is to understand when a modification to the replit.nix file triggers a fresh Nix store build versus reusing a cached environment.

After editing replit.nix to change a package version, a simple restart of the repl does not always result in the updated version being active; the Nix store may retain previous builds, leading to mixed or outdated packages.

Because the documentation does not specify the exact conditions that invalidate the Nix cache, it is unclear whether a restart, a manual rebuild, or another action is required to guarantee reproducibility.

• Does editing replit.nix automatically invalidate the Nix store?
• What specific action (e.g., full rebuild, clearing the Nix cache) guarantees that the new package versions are used?
• Is there a documented way to force a store refresh without deleting the repl?