Free stuck TCP ports in one command — without memorizing `lsof`, `fuser`, and `kill` pipelines

.portkill Free stuck TCP ports in one command — without memorizing lsof, fuser, and kill pipelines. The name reads like .portkill — a small, local dev utility (think .env-style prefix). The CLI binary is still portkill. Published on npm: @burakboduroglu/portkill — install with npm i -g @burakboduroglu/portkill or npx @burakboduroglu/portkill (see Install). When Node or another stack prints EADDRINUSE, .portkill shows who owns the port, lets you preview (--dry-run), then stops only what you intend — or opens a calm local web UI on loopback. Why .portkill Instead of… You get… Copy-pasting lsof / xargs / kill -9 One tool, clear output, safe defaults Guessing PIDs Process name + PID per port Accidentally nuking the wrong thing --dry-run first; --gui with browser confirm Another Electron app Node only; --gui is a tiny HTTP server on 127.0.0.1 / ::1 Install Registry page: npmjs.com/package/@burakboduroglu/portkill. npm i -g @burakboduroglu/portkill portkill --version No global install: npx @