Skip to content
Discussion options

You must be logged in to vote

I am guessing you have a subdirectory containing your package.json file?

Because of how knip runs in the same directory as package.json, it might not load the config which is copied over form qlty/configs/* to project root directory.

This sort of situation can normally be managed by explicitly adding a config flag but for some reason knip doesn't seem to be working with an absolute path to config, i-e knip --no-progress --reporter --config /User/name/work/project/.qlty/configs/knip.json
doesn't work but knip --no-progress --reporter --config .qlty/configs/knip.json works.

The workaround you can do is keep the knip.json file in the same directory as your package.json file (you will need mu…

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@daviddening
Comment options

Answer selected by daviddening
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants