Combining --force and --silent about fkill-cli HOT 7 CLOSED

@ulken The bounty is yours if you submit a test that shows that it's already fixed.

from fkill-cli.

@sindresorhus has rewarded $36.00 to @ulken. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $4.00

from fkill-cli.

Yeah, that's a bug. It should work like you describe. PR welcome :)

from fkill-cli.

@issuehunt has funded $40.00 to this issue.

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

from fkill-cli.

I looked into this. I wasn't able to reproduce it when cloning the repository. However, when installing it from npm, it did indeed fail as described.

Reason: npm is not up-to-date with the repository. To be more precise, dependencies have been updated and fkill in particular. Version 6.2.0 introduced support for the silent option in fkill which fixes this issue.

Fix: Publish a new version with the current repository state to npm

from fkill-cli.

@sindresorhus Thoughts on the above?

from fkill-cli.

@sindresorhus ✅

from fkill-cli.