Added Kill Processes Running od specific ports #1005
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new script command to quickly kill any process running on one or more given ports.
It’s useful for developers who frequently need to stop apps (e.g. Node, Next.js, React, etc.) that are stuck running on ports like 3000, 5000, etc.
The script accepts one or multiple ports as arguments and kills the processes with clear success/failure messages.
Type of change
Screenshot
Dependencies / Requirements
Requires lsof (preinstalled on macOS).
No other dependencies.
Works out of the box on macOS with Raycast.
Checklist