@avelor/drop

Safe directory removal. Validates git state before deleting.

  ✖  drop: uncommitted changes in ./my-project
           commit or stash before deleting

  ✖  drop: unpushed commits in ./my-project
           push before deleting, or use --force

  ✓  ./empty-cache  deleted

drop is rm -rf with a guard. Before deleting, it checks that the directory is either empty, not a git repository, or a git repository with everything committed and pushed. If any check fails, it blocks and tells you why.

Install

npm install -g @avelor/drop

Requires Node.js 18+.

Usage

drop ./old-project        # validate, then delete
drop ./repo --dry-run     # show what would happen without deleting
drop ./broken --force     # skip all validation

Exit code is 0 on success, 1 on any block or error.

Validation order

1. Path exists — errors immediately if not
2. Is a directory — files are not supported (rm handles those)
3. Empty directory — deletes without checks
4. Git repository — blocks if not; use --force to override
5. No uncommitted changes — blocks if git status shows anything
6. Remote configured — blocks if there are commits but no remote
7. All commits pushed — blocks if any local branch has unpushed commits

Each blocked state has its own message explaining what to do next.

Options

--force, -f    skip all validations and delete
--dry-run      show what would happen without deleting
-v, --version
-h, --help

Sudo

drop refuses to run via sudo. If you genuinely need elevated permissions, switch to the root user directly. This prevents accidental destruction of system directories via privilege escalation.

drop: do not run with sudo
      if you need elevated permissions, run as root directly

License

MIT