As a developer, switching between different projects, and often i have to kill diff port. My solution was kill-port, a widely used package to free up ports. But over time, I noticed something frustrating - kill-port was slow. Sometimes, it took up to 20 seconds just to free a port. When you’re in the middle of rapid development, that kind of delay is unacceptable. Trying to Fix the Problem Instead of just dealing with the issue, I decided to take action. I looked into kill-port implementation and found ways to optimize it. Hoping to improve the ecosystem, I created a pull request (PR) to the original repository. But… nothing. No response from the author. Days passed. Weeks passed. Still no update. Building Something Better That’s when I made the decision: If the existing solution isn't improving, why not build my own? That’s how port-client was born. I focused on performance, making it 11x faster than kill-port. Now, instead of waiting 20 seconds, you get your ports freed almost instantly. The Response? Incredible. Turns out, I wasn’t the only one frustrated by slow port management. port-client has now been downloaded nearly 80,000 times—and it's growing fast! Developers around the world are using it to speed up their workflows. Join the Journey This experience taught me something valuable: Problems are just hidden opportunities. What started as an annoyance turned into a widely used package that helps thousands of developers daily. And the journey isn’t over! 🚀 port-client is open-source, and I’d love for you to contribute, suggest improvements, or just give it a try. Check it out: 👉 NPM: port-client👉GitHub: fix2015/port-client Let’s make development faster—one port at a time. ⚡ As a developer, switching between different projects, and often i have to kill diff port. My solution was kill-port , a widely used package to free up ports. But over time, I noticed something frustrating - kill-port was slow . Sometimes, it took up to 20 seconds just to free a port. When you’re in the middle of rapid development, that kind of delay is unacceptable. kill-port kill-port was slow 20 seconds Trying to Fix the Problem Trying to Fix the Problem Instead of just dealing with the issue, I decided to take action. I looked into kill-port implementation and found ways to optimize it. Hoping to improve the ecosystem, I created a pull request (PR) to the original repository. But… nothing. No response from the author. kill-port created a pull request (PR) No response from the author. Days passed. Weeks passed. Still no update. Building Something Better Building Something Better That’s when I made the decision: If the existing solution isn't improving, why not build my own? That’s how port-client was born. If the existing solution isn't improving, why not build my own? port-client I focused on performance, making it 11x faster than kill-port. Now, instead of waiting 20 seconds , you get your ports freed almost instantly. 11x faster 20 seconds The Response? Incredible. The Response? Incredible. Turns out, I wasn’t the only one frustrated by slow port management. port-client has now been downloaded nearly 80,000 times—and it's growing fast! Developers around the world are using it to speed up their workflows. port-client has now been downloaded nearly 80,000 times—and it's growing fast! Join the Journey Join the Journey This experience taught me something valuable: Problems are just hidden opportunities. What started as an annoyance turned into a widely used package that helps thousands of developers daily. Problems are just hidden opportunities. And the journey isn’t over! 🚀 port-client is open-source, and I’d love for you to contribute, suggest improvements, or just give it a try. Check it out: port-client 👉 NPM: port-client 👉 GitHub: fix2015/port-client NPM: port-client GitHub: fix2015/port-client Let’s make development faster—one port at a time. ⚡
