When a port is already in use, there is no interactive way to find it — so I built `port-peek`
The article discusses the creation of a tool called `port-peek` to help developers manage listening ports more efficiently. It addresses the common issue of encountering the EADDRINUSE error and the cumbersome process of identifying and terminating the blocking process. `port-peek` offers an interactive terminal user interface (TUI) that allows users to browse and kill processes with ease.
- ▪Developers often struggle with the EADDRINUSE error, requiring multiple commands to identify and stop processes using specific ports.
- ▪`port-peek` is a zero-dependency tool that provides an interactive TUI for managing listening ports.
- ▪The tool allows users to navigate through listening ports and terminate processes with simple keypresses.
DEV.to (Top) files mainly under programming. We currently carry 4,891 of its stories.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3923619) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Mu Micro Posted on May 21 When a port is already in use, there is no interactive way to find it — so I built `port-peek` #node #cli #devtools #terminal The problem When a port is already in use, developers have to chain together lsof, grep, and kill commands to find and stop the offending process — there is no interactive way to scan all listening ports and act on them in one place. If you've hit EADDRINUSE :::3000 before, you know the ritual: lsof -i :3000, then grep, then kill.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
