Attached: 1 image Data informed decisions when bumping the engine range / peer dependency range of a npm module you maintain? With a new pretty-print and markdown option in my "list-dependents-cli" utility (that I created to drive the canary tests for #neostandard) that's now easy! With it one can now easily list the relevant data of modules dependent on ones module – in the terminal as well as copy it as markdown into an issue. Here's a real world example: https://github.com/eslint-community/eslint-utils/issues/233#issuecomment-2355754090