Configuration
Defaults
Knip has good defaults and aims for “zero config”. Here’s a simplified version of the default configuration:
Entry files are the starting point for Knip to find more source files and external dependencies.
Location
By default, Knip will look for a configuration file with the following names:
knip.json
knip.jsonc
.knip.json
.knip.jsonc
knip.ts
knip.js
knip.config.ts
knip.config.js
package.json
(in the"knip"
property)
If you want to use a custom file name or path, use the --config
flag:
Customize
Your project structure may not match the default entry
and project
files.
Here’s an example custom configuration to include .js
files in the scripts
folder:
If you override the entry
file patterns, you may also want to override
project
file patterns. The set of project files is used to determine what
files are unused. The project
patterns can also be negated to exclude files
from the analysis. Also see configuring project files.
The values you set override the default values, they are not merged.
Knip looks in many places for entry files. Learn more about this in the next page about entry files.
Configuration Options
See the configuration reference documentation.
What’s next?
The best way to understand Knip and what it can do for you is to read the pages in the “Understanding Knip” sections, starting with entry files.
Want to learn more about some of the main features?
- Working with monorepos & workspaces.
- Learn more about production mode.
Having troubles configuring Knip?
Search this website using the bar at the top (Ctrl+K
or ⌘+K
).
ISC License © 2024 Lars Kappert