Question 1

How to use npkill to delete all node_modules in a specific folder?

Accepted Answer

Run `npkill -d /path/to/folder` to scan that directory, then use the interactive CLI to select and delete. For automatic deletion without prompts, add the `--delete-all` flag, but use caution to avoid removing needed dependencies.

Question 2

Can npkill break my system if I delete the wrong node_modules?

Accepted Answer

npkill highlights system-critical directories with warnings, but it's not foolproof. Always review the list before deletion, especially for global installations, to prevent breaking applications that rely on those dependencies.

Question 3

npkill vs manual deletion with rm -rf: which is better?

Accepted Answer

npkill is superior for scanning multiple directories quickly and providing size insights, while manual deletion offers more control but is inefficient for bulk operations. Use npkill for discovery and batch cleanup, but verify critical paths first.

Question 4

How to automate npkill cleanup on a schedule?

Accepted Answer

Use the `--json` output to generate a list of directories, then write a script that filters by size or age and deletes them. Integrate this script with cron jobs or task schedulers for regular maintenance.

Question 5

Does npkill work with pnpm or Yarn 2 projects?

Accepted Answer

npkill targets node_modules directories, so it should work, but be aware that pnpm uses symlinks and Yarn 2 may have different structures, which could affect size calculations and deletion outcomes. Test in a safe environment first.

Question 6

How to exclude certain directories from npkill scans?

Accepted Answer

Use the `--exclude` flag with a comma-separated list, e.g., `npkill --exclude "ignore1, ignore2"`. This prevents scanning specified paths, useful for skipping backup or critical folders.

npkill

What is npkill?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions