How Replit handles dependency isolation

Each Repl you create runs in its own containerized environment powered by Nix. This means Project A can use Node.js 18 while Project B uses Node.js 20, and they will never interfere with each other. System-level packages (compilers, runtimes, system libraries) are managed by Nix, while language-level packages (npm modules, pip packages) are managed by their respective package managers within each Repl's filesystem. Even on the same Replit account, installing a package in one Repl has zero effect on any other Repl.

Click the three-dot menu at the top of the file tree and select Show hidden files. Open the replit.nix file in your project root. This file uses the Nix expression language to declare system-level packages. The deps array lists every package available in your environment. If a package is not listed here, it will not be available in the Shell or to your application. The pkgs argument provides access to the entire Nixpkgs repository, which contains over 80,000 packages.

1{ pkgs }: {
2  deps = [
3    pkgs.nodejs-20_x
4    pkgs.python311
5    pkgs.nodePackages.typescript-language-server
6  ];
7}

To add a new system-level package, search for its name at search.nixos.org/packages, then add it to the deps array in replit.nix. For example, adding pkgs.ffmpeg gives you the ffmpeg command-line tool for video processing, which is not available by default. After saving the file, type exit in the Shell and reopen it to reload the Nix environment. You can also add packages through the Dependencies GUI in the Tools dock, which edits replit.nix for you.

1{ pkgs }: {
2  deps = [
3    pkgs.nodejs-20_x
4    pkgs.python311
5    pkgs.ffmpeg
6    pkgs.imagemagick
7    pkgs.sqlite
8  ];
9}

When you run npm install in a Node.js project, packages are installed into the node_modules folder inside your Repl. When you run pip install in a Python project, packages go into a site-packages directory scoped to your Repl's environment. These directories are part of your Repl's filesystem and are completely separate from other Repls. Your package.json or requirements.txt file serves as the declaration of language-level dependencies, while replit.nix handles the system-level tools.

1# Node.js — packages install to ./node_modules/
2npm install express
3
4# Python — packages install to the Repl's site-packages
5pip install flask
6
7# Verify installed location
8npm list express
9pip show flask

The Nix channel in your .replit file determines which snapshot of the Nixpkgs repository your project uses. Different channels offer different package versions. For example, stable-23_11 includes different versions of Node.js and Python than stable-24_05. Setting a specific channel pins your system packages to a known set of versions, ensuring your environment does not change unexpectedly when Replit updates its defaults.

1# In .replit file:
2[nix]
3channel = "stable-24_05"

The most common Nix error is nix error: building nix env: exit status 1, which usually means a package name is wrong, the Nix channel does not include the requested package version, or an unfree package is referenced without enabling unfree packages. To diagnose, run cat /run/replit/env/error in the Shell to see the full error output. Fix the issue in replit.nix, save, and restart Shell with exit. If the environment is completely broken, you can reset it through the Dependencies tool or by reverting replit.nix via File History.

1# Diagnose Nix errors:
2cat /run/replit/env/error
3
4# Check which packages are currently loaded:
5echo $PATH | tr ':' '\n' | grep nix
6
7# Verify a specific tool is available:
8which node
9which python3