Why Replit builds are slow

Open the Shell from the Tools dock and run your install command manually (e.g., npm install or pip install -r requirements.txt) to see how long it takes. Then check your storage usage by clicking the Resources panel icon (stacked computers). Large node_modules folders, duplicate dependencies, and oversized Nix environments are the three most common culprits. Run du -sh node_modules to see the exact size. Anything over 500 MB is a warning sign.

1# Check node_modules size
2du -sh node_modules
3
4# Check total project size
5du -sh .
6
7# List largest directories
8du -h --max-depth=1 | sort -rh | head -10

Audit your package.json for dependencies you no longer use. Every unnecessary package adds to install time and storage. Run npx depcheck to find unused packages in Node.js projects. For Python, check your imports against requirements.txt manually. Remove anything that is not actively imported in your source code. This single step can dramatically reduce install times.

1# Find unused Node.js dependencies
2npx depcheck
3
4# Remove an unused package
5npm uninstall unused-package-name
6
7# Clean npm cache to free storage
8npm cache clean --force

The onBoot command in your .replit file runs every time the Repl wakes up. By placing your install command here, Replit caches installed packages across restarts instead of re-downloading them each time you click Run. Open the .replit file (enable Show hidden files in the file tree menu if you do not see it) and add an onBoot line. This is especially important for Autoscale deployments where cold starts re-initialize the environment.

1# Add this to your .replit file
2onBoot = "npm install --prefer-offline"

Replit uses Nix for system-level packages. An outdated Nix channel forces unnecessary recompilation. Open your .replit file and check the [nix] channel value. Update it to a recent stable channel like stable-24_05. Also ensure your replit.nix file only includes packages you actually need. Replit maintains a large prebuilt cache for common packages, so using standard package names avoids compilation from source. After changes, run exit in Shell to reload the Nix environment.

1# In .replit, update the Nix channel
2[nix]
3channel = "stable-24_05"
4packages = ["nodejs-20_x"]

If your Run command includes both a build step and a start step, the build runs every time you click Run. Separate these by putting the build step in onBoot or a dedicated build script and keeping only the start command in run. For deployments, use the [deployment] section to define separate build and run commands. This prevents redundant compilation during development.

1# .replit configuration
2onBoot = "npm install --prefer-offline && npm run build"
3run = "node dist/index.js"
4
5[deployment]
6build = ["npm", "run", "build"]
7run = ["node", "dist/index.js"]

Click the Resources panel icon (stacked computers) in the left sidebar while your build runs. Watch RAM and CPU usage in real time. If RAM usage spikes near the limit (2 GiB on Starter, 8 GiB on Core), your build may crash with an out-of-memory error. For Node.js projects, you can limit memory usage with the --max-old-space-size flag. If builds consistently max out resources, consider upgrading your plan or reducing the scope of each build.

1# Set Node.js memory limit for builds
2NODE_OPTIONS="--max-old-space-size=4096" npm run build