Define and implement a strategy for "obscure" things like husky + lint-staged about knip HOT 3 CLOSED

What might be missing?

According to the husky docs:

{
  "scripts": {
    "prepare": "husky install"
  }
}

Or in postinstall. This way, it would be a regular catch for Knip to see husky is used. However, in the blockprotocol repo, husky is not used or referenced anymore, it was only used to install the Git hooks.

Just saying, the job of plugins is mostly to find dependencies of, in this case, husky, which it finds by scanning the Git hooks themselves (which contains the lint-staged dependency in the blockprotocol repo).

from knip.

Done in 73445e8 (v1.5.0)

from knip.

Hmm still seeing husky as an unused dev dependency in blockprotocol/blockprotocol#895 after upgrading to 1.6.1: https://github.com/blockprotocol/blockprotocol/actions/runs/3940673346/jobs/6742082250#step:8:39. What might be missing?

from knip.