@knip/mcp 0.0.18 → 0.0.20

package/src/docs/guides/troubleshooting.md

@@ -23,8 +23,7 @@ Knip is intentionally strict to maximize its potential. It may initially report
 many unused files. However, getting this right will result in great reports and
 tidy codebases.
 
-If it doesn't come your way at the first try, remember that often only a small
-change go a long way towards success.
+If it doesn't work out at first, a small change can go a long way.
 
 :::
 
@@ -33,9 +32,8 @@ change go a long way towards success.
 Knip reports lint issues in your codebase. See [handling issues][5] to deal with
 the reported issues.
 
-If Knip reports false positives and you're considering filing a GitHub issue,
-please do! It'll make Knip better for everyone. Please read [issue
-reproduction][6] first.
+If you're considering filing an issue, please read [issue reproduction][6]
+first.
 
 Exit code 1 indicates a successful run, but lint issues were found.
 
@@ -47,8 +45,7 @@ See [known issues][7] as it may be listed there and a workaround may be
 available. If it isn't clear what's throwing the exception, try another run with
 `--debug` to locate the cause of the issue with more details.
 
-If Knip throws an exception and you're considering filing a GitHub issue, please
-do! It'll make Knip better for everyone. Please read [issue reproduction][6]
+If you're considering filing an issue, please read [issue reproduction][6]
 first.
 
 Exit code 2 indicates an exception was thrown by Knip.
@@ -93,7 +90,7 @@ a regex that works too:
 
 <img src="/screenshots/trace-dependency.png" alt="trace dependency" class="mw500" />
 
-Use [--workspace \[dir\]][8] to filter accordingly.
+Use [--workspace \[filter\]][8] to filter accordingly.
 
 #### Legend
 
@@ -124,10 +121,10 @@ to [open an issue on GitHub][14].
 [2]: #exceptions-thrown-by-knip
 [3]: #debug
 [4]: #trace
-[5]: ../guides/handling-issues.md
+[5]: ../guides/handling-issues.mdx
 [6]: ./issue-reproduction.md
 [7]: ../reference/known-issues.md
-[8]: ../reference/cli.md#--workspace-dir
+[8]: ../reference/cli.md#--workspace-filter
 [9]: ../explanations/entry-files.md
 [10]: ../explanations/plugins.md
 [11]: ../features/production-mode.md

package/src/docs/guides/using-knip-in-ci.md

@@ -21,10 +21,12 @@ on: push
 jobs:
   lint:
     runs-on: ubuntu-latest
-    name: Ubuntu/Node v20
+    name: Ubuntu/Node v24
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
+        with:
+          node-version: 24
       - name: Install dependencies
         run: npm install --ignore-scripts
       - name: Run knip
@@ -33,22 +35,16 @@ jobs:
 
 ## Notes
 
-In CI environments, the [--no-progress][1] flag is set automatically.
-
-## Related features
-
-- [--cache][2]
-- [--max-issues][3]
-- [--no-exit-code][4]
-- [--reporter][5]
-
-## Related reading
-
-- [Why use Knip?][6]
-
-[1]: ../reference/cli.md#--no-progress
-[2]: ../reference/cli.md#--cache
-[3]: ../reference/cli.md#--max-issues
-[4]: ../reference/cli.md#--no-exit-code
-[5]: ../reference/cli.md#--reporter-reporter
-[6]: ../explanations/why-use-knip.md
+- Use [--cache][1] to speed up consecutive runs (default location:
+  `./node_modules/.cache/knip`).
+- See [Reporters][2] including the GitHub Actions reporter.
+- Consider running Knip twice: a default run and a [production mode][3] run.
+- See [CLI arguments → Output][4] for some relevant options such as
+  `--treat-config-hints-as-errors` and `--no-exit-code`.
+- In CI environments, the [--no-progress][5] flag is set automatically.
+
+[1]: ../reference/cli.md#--cache
+[2]: ../features/reporters.md
+[3]: ../features/production-mode.md
+[4]: ../reference/cli.md#output
+[5]: ../reference/cli.md#--no-progress

package/src/docs/index.mdx

@@ -31,7 +31,7 @@ import Contributors from '../../components/Contributors.astro';
 
 :::section{.badges}
 
-[![NPM Version][2]][1] [![NPM Downloads][3]][1] [![GitHub Repo   stars][5]][4]
+[![NPM Version][2]][1] [![NPM Downloads][3]][1] [![GitHub Repo stars][5]][4]
 
 :::
 
@@ -138,10 +138,10 @@ A curated selection of articles about Knip, most recent first:
 [3]: https://img.shields.io/npm/dm/knip?color=f56e0f
 [4]: https://github.com/webpro-nl/knip
 [5]: https://img.shields.io/github/stars/webpro-nl/knip?style=flat&color=f56e0f
-[6]: ./sponsors
+[6]: /sponsors
 [7]: https://webpro.nl/hire-me
 [8]: ./reference/plugins.md
-[9]: ./playground
+[9]: /playground
 [10]: ./guides/troubleshooting.md
 [11]: https://www.jamesshopland.com
 [12]: https://blog.val.town/gardening-dependencies

package/src/docs/overview/configuration.md

@@ -52,10 +52,9 @@ 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. See [configuring project files][1] for details.
+The set of `project` files determines the analysis scope. Use negated `project`
+patterns to exclude files from the analysis. See [configuring project files][1]
+for details.
 
 The values you set override the default values, they are not merged.
 
@@ -64,8 +63,9 @@ The values you set override the default values, they are not merged.
 Be specific with `entry` files. Minimize the number of entry files and wildcards
 for better results.
 
-Plugins are enabled automatically, and set entry files for you. Such as for
-Next.js, Astro, Remix, Vitest, Playwright and many more.
+Plugins are enabled automatically, and their entry files are added
+automatically. Such as for Next.js, Astro, Remix, Vitest, Playwright and many
+more.
 
 :::
 

package/src/docs/overview/features.md

@@ -19,7 +19,7 @@ Also see [related tooling][2].
 | Configuration hints          | Display configuration hints to keep `knip.json` tidy                  |
 | [Debug][7]                   | Use `--debug` for troubleshooting                                     |
 | [Filters][8]                 | Exclude or focus on specific issue types                              |
-| [Format][9]                  | Add `--format` to `--fix` and auto-format modified files              |
+| [Format][9]                  | Use `--format` with `--fix` to auto-format modified files             |
 | [JSDoc tags][10]             | Tag and exclude specific exports from the report                      |
 | [Memory usage][11]           | Use `--memory` for detailed memory usage insights                     |
 | [Monorepos][12]              | Workspaces are first-class citizen                                    |
@@ -33,10 +33,10 @@ Also see [related tooling][2].
 | [Rules][20]                  | Exclude or focus on specific issue types                              |
 | [Script parser][21]          | Shell scripts and `package.json` contain entry paths and dependencies |
 | [Source mapping][22]         | Map `dist` files back to `src` files                                  |
-| [Strict mode][23]            | Use `--strict` to isolate workspaces and consider only `dependencies` |
+| [Strict mode][23]            | Use `--strict` to tighten and lint only production `dependencies`     |
 | [Trace][24]                  | Trace exports to find where they are used                             |
 | [Watch mode][25]             | Use `--watch` for live updates of unused files and exports            |
-| [Workspace][26]              | Use `--workspace` to lint a single workspace in a monorepo            |
+| [Workspace][26]              | Use `--workspace` to filter workspaces in a monorepo                  |
 
 [1]: ../reference/issue-types.md
 [2]: ../reference/related-tooling.md
@@ -44,7 +44,7 @@ Also see [related tooling][2].
 [4]: ../reference/cli.md#--cache
 [5]: ../guides/working-with-commonjs.md
 [6]: ../features/compilers.md
-[7]: ../guides/troubleshooting.md#issues-reported-by-knip
+[7]: ../guides/troubleshooting.md#debug
 [8]: ../features/rules-and-filters.md#filters
 [9]: ../features/auto-fix.mdx#format
 [10]: ../reference/jsdoc-tsdoc-tags.md
@@ -63,4 +63,4 @@ Also see [related tooling][2].
 [23]: ../features/production-mode.md#strict-mode
 [24]: ../guides/troubleshooting.md#trace
 [25]: ../reference/cli.md#--watch
-[26]: ../features/monorepos-and-workspaces#lint-a-single-workspace
+[26]: ../features/monorepos-and-workspaces.md#filter-workspaces

package/src/docs/overview/getting-started.mdx

@@ -75,9 +75,18 @@ Knip will lint your project and report unused dependencies, exports and files.
 If the output makes sense to you, feel free to go to the next page:
 [configuration][2].
 
+:::tip
+
+Try the [Knip Editor Extension][3]! Let your coding agent use the built-in MCP
+Server and create a custom `knip.json` for you.
+
+:::
+
 ## Too Much?
 
-In large or complex codebases the output might be overwhelming. Start by
+In large or complex codebases the output might be overwhelming.
+
+Start by
 limiting the number of shown issues per type:
 
 <Tabs syncKey="pm">
@@ -108,12 +117,12 @@ limiting the number of shown issues per type:
 
 The output is easier to digest and may include some configuration hints to get
 an idea of what's left to configure. Many unused files? Go to [configuration][2]
-and follow up with [troubleshooting][3] if needed.
+and follow up with [troubleshooting][4] if needed.
 
 :::tip
 
 Do not use the `ignore` option just to get rid of unwanted output. Read
-[Configuring Project Files][4] to get the most out of Knip.
+[Configuring Project Files][5] to get the most out of Knip.
 
 :::
 
@@ -191,5 +200,6 @@ already.
 
 [1]: /playground
 [2]: ./configuration.md
-[3]: ../guides/troubleshooting.md
-[4]: ../guides/configuring-project-files.md
+[3]: ../blog/for-editors-and-agents.md
+[4]: ../guides/troubleshooting.md
+[5]: ../guides/configuring-project-files.md