GitShow/sindresorhus/fkill-cli
sindresorhus

fkill-cli

Fabulously kill processes. Cross-platform.

by sindresorhus
clicli-appcross-platformfabulousjavascriptkillnodejsprocess
Star on GitHubForknpm

JavaScript

7.0k stars212 forks12 contributorsQuiet · 7mo agoSince 2015v9.0.0MIT

Meet the team

See all 12 on GitHub →
sindresorhus
sindresorhus81 contributions
kevva
kevva7 contributions
stroncium
stroncium4 contributions
dnbkr
dnbkr3 contributions
xxczaki
xxczaki1 contribution
jopemachine
jopemachine1 contribution
Hammster
Hammster1 contribution
jankdc
jankdc1 contribution

Languages

View on GitHub →
JavaScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

4 of 6 standards met

Community profile →
71
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 2 in progress · Last activity 7mo ago
See all on GitHub →
sindresorhus
Smart modeOpenIssue

Currently there's a lot of useless processes in interactive mode that I would never care to close. Like all the Chrome helper processes. These makes it harder to find processes I actually want to close. With some simple heuristics I think we could hide away most of those useless processes. Should smart mode be default when using the interactive UI? What processes needs hiding? ~~Google Chrome Helper~~ (done) 2BUA8C4S2C.com.agilebits.onepassword-osx-helper zsh IssueHunt Summary Backers (Total: $40.00) issuehunt ($40.00) Submitted pull Requests #1 Group duplicate processes in interactive mode #1 Add explicit kill-all choices for duplicate processes Become a backer now! Or submit a pull request to get the deposits! Tips Checkout the Issuehunt explorer to discover more funded issues. Need some help from other developers? Add your repositories on IssueHunt to raise funds.

sindresorhus · 1mo ago
MapleQiAN
Add bulk choices to interactive process searchOpenPR

Adds bulk entries to the interactive process search so filtered results can be killed together: show an "All matching processes" entry when a search returns multiple processes show "All processes" entries when the filtered results include duplicate process names keep the existing single-process choices unchanged document the interactive bulk choice and cover the choice generation in tests Addresses #6. Fixes #21. Tests: npm test

MapleQiAN · 1mo ago
Kabi10
Add interactive kill-all process groupsOpenPR

This adds a kill-all option for same-name processes in interactive mode. What changed: Groups same-name processes in the interactive search results. Shows a clear "Kill all N process-name processes" entry for duplicate process names. Selecting that group passes all matching PIDs through the existing kill sequence. Adds a focused AVA test for grouped process choices. This addresses the interactive kill-all use case from #21 and also helps with the same-name process grouping discussed in #6. Verification: npm test Closes #21

Kabi10 · 2mo ago

Recent fixes

View closed PRs →
phusi319
Add kill-all option in interactive modeMergedPR

Closes #21 Problem When multiple processes share the same name (e.g. , ), users have to run repeatedly to kill each one individually. This was the most requested enhancement (funded \ on IssueHunt). Solution When searching in interactive mode, if 2 or more processes match the search term, a "Kill all" option appears at the top of the results list: Selecting "Kill all" kills every matching process at once. Individual process selection continues to work exactly as before. Design decisions Minimal change: Only 12 lines added to no new dependencies, no architectural changes Only appears when useful: The option only shows when there's a search term AND 2+ matches. No risk of accidentally killing everything Works with existing kill flow: Uses the same which already handles arrays of PIDs, including the force-kill fallback prompt Consistent with maintainer guidance: @sindresorhus suggested a shortcut to "kill all with the same name" this surfaces that as a first-class search result option Changes : Add "Kill all" option to search results when multiple processes match : Document the feature in help text Testing All existing tests pass () Zero new lint warnings

phusi319 · 3mo ago
zymr-keshav
Aggregate Error in mac os HighSierraClosedIssue

Macos v 10.1.3.3 ( High Sierra) There is a process running on the port 8083 ; I have checked from command and When I try to kill a process using port number than it gives following error: fkill :8083 AggregateError: Error: Killing process 64708 failed: Process doesn't exist at Array.map () at processExists.all.then.then (/usr/local/lib/node_modules/fkill-cli/node_modules/fkill/index.js:83:10) at at processExists.all.then.then (/usr/local/lib/node_modules/fkill-cli/node_modules/fkill/index.js:83:10) at at process._tickCallback (internal/process/next_tick.js:188:7)

zymr-keshav · 7mo ago
rauchg
Smart case supportClosedIssue

It might be interesting to use vi-style smart case. If you include at least one uppercase letter, the search becomes case sensitive. Also implemented by : https://github.com/rauchg/spot#smart-case

rauchg · 7mo ago
Structured data for AI agents

Repository: sindresorhus/fkill-cli. Description: Fabulously kill processes. Cross-platform. Stars: 6995, Forks: 212. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Topics: cli, cli-app, cross-platform, fabulous, javascript, kill, nodejs, process, unicorns. Latest release: v9.0.0 (7mo ago). Open PRs: 2, open issues: 5. Last activity: 7mo ago. Community health: 71%. Top contributors: sindresorhus, kevva, stroncium, dnbkr, xxczaki, jopemachine, Hammster, jankdc, mokkabonna, ulken and others.

·@ofershap

Replace github.com with gitshow.dev