Easiest way to kill hanging processes using port numbers - on any operating systems
To setup the package/project in your local, following are the pre-requisites: [x] node >= v10.x [x] npm >= 7.x
To use the npm package of the port-kill using npx:
# Example : npx port-kill
> npx port-kill
If you are interested to only check the health or if port is alive or not:
> npx port-kill --health
Pull Requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update and keep the code in sync time to time.
FAQs
Script to kill the port/process
The npm package port-kill receives a total of 65 weekly downloads. As such, port-kill popularity was classified as not popular.
We found that port-kill demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Benign-looking npm packages split malicious functionality across a dependency chain that deploys a cross-platform RAT targeting Alibaba developers.
Research
/Security News
Two Joyfill npm beta releases contain an import-time implant that uses blockchain transactions to retrieve a remote-access trojan.
Security News
Socket releases free Certified Patches for high-severity Nuxt vulnerabilities, including server-side remote code execution through server island props.