🧩 dependency used only via cli

[m-ronchi]

Discuss anything related to Knip

Hi,
I have a dependency (node-pg-migrate) that I use both in dev (inside a package.json script) and in prod (by just including it in the docker image, then I run it using npx node-pg-migrate as a command inside that image).

the problem is that by default, npx knip works, but npx knip --strict reports it as an unused dependencies. if I add it to config ignoreDependencies, then npx knip --strict works but npx knip reports it as Unused item in ignoreDependencies.

which is the correct way to make both commands work?

[webpro]

Some ideas:

• The "unused item" is not an error, but a warning (i.e. does not cause non-zero exit code, so won't make CI fail)
• Use two different configurations, e.g. knip and knip --strict -c knip.strict.json or vice versa
• Move node-pg-migrate to devDependencies

[m-ronchi]

Hi, thanks for the ideas.

1. I am not using it in CI (for now, in this project) but as CLI and visually the output looks the same (with yellow header)
2. 2 different configs also is not as friendly when I run it manually (also will need to keep them in sync)
3. node-pg-migrate is actually used in prod, maybe I can transition it to dev when I go back to this particular project.

I think I stay with 1 for now and then try 3 later, but on the knip side, it would be nice a way to declare npm packages' bin as entrypoint (another example: ts-node)

[webpro]

Re. 2, you could use knip.ts and load one from the other

I'll look into making the output visually more clear

[webpro]

🚀 This issue has been resolved in v5.44.0. See Release 5.44.0 for release notes.

Using Knip in a commercial project? Please consider becoming a sponsor.