@knip/mcp 0.0.18 → 0.0.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.18",
+  "version": "0.0.19",
   "description": "Knip MCP Server",
   "type": "module",
   "bin": {
@@ -20,15 +20,15 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/webpro-nl/knip",
+    "url": "git+https://github.com/webpro-nl/knip.git",
     "directory": "packages/mcp-server"
   },
   "author": "Lars Kappert <lars@webpro.nl>",
   "license": "ISC",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.25.1",
+    "@modelcontextprotocol/sdk": "^1.25.3",
     "zod": "^4.1.11",
-    "knip": "^5.83.0"
+    "knip": "^5.84.0"
   },
   "engines": {
     "node": ">=18.18.0"

package/src/docs/blog/for-editors-and-agents.md

@@ -7,32 +7,34 @@ sidebar:
 
 _Published: 2025-12-17_
 
-Three years in, Knip has founds its place in [over 10.000 projects][1] and is
+Three years in, Knip has found its place in [over 10.000 projects][1] and is
 downloaded [over 18M times/month][2]. A long period of steady growth in usage
 and stability allows Knip to become more accessible to more people. That's why
-I'm excited and proud to introduce the brand new VS Code Extension **and** MCP
-Server. For humans and coding agents alike, Knip will help keep your codebases
-tidy.
+I'm excited and proud to introduce the brand new [Editor Extension][3] **and**
+MCP Server. For humans and coding agents alike, Knip will help keep your
+codebases tidy.
 
 Don't forget... Knip it before you ship it!
 
-## VS Code/Open VSX Extension
+## Editor Extension
 
 This one is for you.
 
-[The usual suspects][3] like red squiggles for unused exports are there. What
+[The usual suspects][4] like red squiggles for unused exports are there. What
 really moves the needle for DX with Knip's module graph is **navigation**. A
-completely unique way to view & fly through codebases for developers who care.
-Connect the dots during development and refactors, while keeping things in
-check. We're starting out with [3 key features][4]:
+completely unique way to view & fly through codebases. Connect the dots during
+development and refactors, while keeping things in check. We're starting out
+with [3 key features][5]:
 
 1. **Hover over Export** for import & usage locations
 2. **Imports Tree View** for direct links to implementations
 3. **Exports Tree View** for direct links to import & usage locations
 
-Find [Knip on the VS Code Marketplace][5].
+The extension has a [built-in MCP Server][6] with a command and resources to
+configure Knip for you, _completely automated_.
 
-**EDIT:** Or find [Knip on the Open VSX Registry][6].
+Find [Knip on the VS Code Marketplace][7] and find [Knip in the Open VSX
+Registry][8].
 
 ## MCP Server
 
@@ -41,7 +43,7 @@ coding agent to "configure knip" and it will RTFM so you don't have to. Using a
 newer model like Opus 4.5 or GPT 5.2 results in an optimized `knip.json` file
 and an uncluttered codebase.
 
-The [MCP Server is available][7] separately and built into the VS Code
+The [MCP Server is available][9] separately and built into the VS Code
 Extension.
 
 ## Language Server
@@ -53,25 +55,25 @@ information. Queries like "where is an export imported" or "is this import part
 of a circular dependency" are just scratching the surface here.
 
 Extensions for other IDEs can be built on top. See
-[language-server/README.md][8]
+[language-server/README.md][10]
 
 ## Screenshots
 
-- [Lint Findings][3]
-- [Imports & Exports][4]
-- [Contention][9]
-  - [Circular Dependencies][10]
-  - [Conflicts][11]
-  - [Branching][12]
-- [VS Code Extension Settings][13]
+- [Lint Findings][4]
+- [Imports & Exports][5]
+- [Contention][11]
+  - [Circular Dependencies][12]
+  - [Conflicts][13]
+  - [Branching][14]
+- [VS Code Extension Settings][15]
 
 ### Lint Findings
 
-![Lint Findings][14]
+![Lint Findings][16]
 
 ### Imports & Exports
 
-![hover][15]
+![hover][17]
 
 ### Contention
 
@@ -83,7 +85,7 @@ branched/diamond-shaped import chains.
 
 If an import is part of a circular dependency, Knip will display:
 
-![Circular Dependencies][16]
+![Circular Dependencies][18]
 
 #### Conflicts
 
@@ -91,7 +93,7 @@ TypeScript shows direct conflicts when importing or re-exporting the same named
 export from different files. Except when the problem is more subtle and the
 chain spans more than one file. Knip warns:
 
-![Conflicts][17]
+![Conflicts][19]
 
 #### Branching
 
@@ -99,29 +101,31 @@ Branched or diamond-shaped imports chains indicate unnecessary re-exports and
 complexity. They help to untangle large codebases and shrink or get rid of
 barrel files. Knip warns:
 
-![Branching][18]
+![Branching][20]
 
 ### VS Code Extension Settings
 
-![VS Code Extension Settings][19]
+![VS Code Extension Settings][21]
 
 [1]: https://github.com/webpro-nl/knip/network/dependents
 [2]: https://www.npmjs.com/package/knip
-[3]: #lint-findings
-[4]: #imports--exports
-[5]: https://marketplace.visualstudio.com/items?itemName=webpro.vscode-knip
-[6]: https://open-vsx.org/extension/webpro/vscode-knip
-[7]: https://www.npmjs.com/package/@knip/mcp
-[8]:
+[3]: #editor-extension
+[4]: #lint-findings
+[5]: #imports--exports
+[6]: #mcp-server
+[7]: https://marketplace.visualstudio.com/items?itemName=webpro.vscode-knip
+[8]: https://open-vsx.org/extension/webpro/vscode-knip
+[9]: https://www.npmjs.com/package/@knip/mcp
+[10]:
   https://github.com/webpro-nl/knip/blob/main/packages/language-server/README.md
-[9]: #contention
-[10]: #circular-dependencies
-[11]: #conflicts
-[12]: #branching
-[13]: #vs-code-extension-settings
-[14]: /screenshots/editors-and-agents/diagnostics.webp
-[15]: /screenshots/editors-and-agents/imports-exports.webp
-[16]: /screenshots/editors-and-agents/circular-dependency.webp
-[17]: /screenshots/editors-and-agents/conflict.webp
-[18]: /screenshots/editors-and-agents/branch.webp
-[19]: /screenshots/editors-and-agents/vscode-extension-settings.webp
+[11]: #contention
+[12]: #circular-dependencies
+[13]: #conflicts
+[14]: #branching
+[15]: #vs-code-extension-settings
+[16]: /screenshots/editors-and-agents/diagnostics.webp
+[17]: /screenshots/editors-and-agents/imports-exports.webp
+[18]: /screenshots/editors-and-agents/circular-dependency.webp
+[19]: /screenshots/editors-and-agents/conflict.webp
+[20]: /screenshots/editors-and-agents/branch.webp
+[21]: /screenshots/editors-and-agents/vscode-extension-settings.webp

package/src/docs/blog/knip-v4.mdx

@@ -144,6 +144,6 @@ Remember, Knip it before you ship it! Have a great day ☀️
 
 [1]: ./slim-down-to-speed-up.md
 [2]: ../features/compilers.md
-[3]: ../guides/issue-reproduction
+[3]: ../guides/issue-reproduction.md
 [4]: https://github.com/sponsors/webpro
-[5]: ../reference/cli#--experimental-tags
+[5]: ../reference/cli.md#--experimental-tags

package/src/docs/blog/two-years.mdx

@@ -101,7 +101,7 @@ Thanks to Joshua Goldberg for [emoji-blast][7]! 🎉
 [1]: https://www.npmjs.com/package/exportman/v/0.0.1
 [2]: /cow-with-orange-scissors-van-gogh-style.webp
 [3]: https://github.com/webpro-nl/knip/releases/tag/5.31.0
-[4]: ../features/auto-fix.md
+[4]: ../features/auto-fix.mdx
 [5]: https://github.com/unjs/jiti
 [6]: /sponsors
 [7]: https://www.emojiblast.dev

package/src/docs/docs/explanations/comparison-and-migration.md

@@ -36,6 +36,8 @@ depcheck
 knip --dependencies
 ```
 
+**Project status**: The project is archived and recommends Knip.
+
 ### unimported
 
 > Find and fix dangling files and unused dependencies in your JavaScript
@@ -95,6 +97,8 @@ Use `knip --exports` to also include class and enum members.
 on a single `tsconfig.json` file (`includes` and `excludes`) and requires no
 configuration. It removes the `export` keyword or the whole export declaration.
 
+**Project status**: The project is archived and recommends Knip.
+
 ## Related projects
 
 Additional alternative and related projects include:

package/src/docs/docs/explanations/plugins.md

@@ -86,8 +86,8 @@ plugins contain `package.json` in the list of `config` files.
 
 :::tip[Summary]
 
-Plugins parse `config` files to find external dependencies. Knip uses this to
-determine unused and unlisted dependencies.
+Plugins load configuration files to find referenced dependencies, and determine
+unused and unlisted dependencies.
 
 :::
 
@@ -304,6 +304,23 @@ playwright test -c playwright.web.config.ts
 
 Please see [script parser][10] for more details.
 
+## Config File Location
+
+If configuration files aren't in their default location and they are not
+referenced through some script like `vite -c ./dir/vite.config.ts`, then make
+sure to tell Knip about it. Two examples:
+
+```json title="knip.jsonc"
+{
+  "playwright": { "config": ["e2e/playwright.config.ts"] },
+  "vite": "packages/*/vite.config.ts" // shorthand without `config` and array notation
+}
+```
+
+This is common in projects where a directory like `packages/lib` is not an
+actual workspace with a `package.json` file. Also see [integrated monorepos][11]
+for similar cases.
+
 ## Summary
 
 :::tip[Summary]
@@ -327,3 +344,4 @@ Plugins are configured with two distinct types of files:
 [8]: ../reference/plugins/vitest.md
 [9]: ../guides/handling-issues.mdx#conditional-or-dynamic-dependencies
 [10]: ../features/script-parser.md
+[11]: ../features/integrated-monorepos.md

package/src/docs/docs/features/auto-fix.mdx

@@ -42,10 +42,10 @@ knip --fix --allow-remove-files
 
 Use `--fix-type` to fix only specific issue types:
 
-- `files`
+- `dependencies`
 - `exports`
 - `types`
-- `dependencies`
+- `files`
 - `catalog`
 
 Example:

package/src/docs/docs/guides/issue-reproduction.md

@@ -73,17 +73,17 @@ Other solutions to share a minimal and reproducible case may work well too,
 including:
 
 - A public repository on e.g. GitHub or GitLab.
-- A new [fixtures folder in the Knip repository][9].
+- A pull request with a new [test][9] and/or [fixture folder][10].
 
 The goal is to have an easy and common understanding and reproduction. If you're
 unable to create a reproduction using one of the methods described then please
-clearly explain this in the issue or [contact me][10].
+clearly explain this in the issue or [contact me][11].
 
 ## Pull Request
 
 The optimal way is to add fixtures and failing tests to the Knip repository, and
 open a pull request to discuss the issue! Also see [instructions for
-development][11].
+development][12].
 
 [1]: https://github.com/webpro-nl/knip/issues?q=is%3Aissue
 [2]: https://knip.dev/reference/known-issues
@@ -97,6 +97,7 @@ development][11].
   https://stackblitz.com/github/webpro-nl/knip/tree/main/templates/issue-reproduction/monorepo
 [7]: https://codesandbox.io
 [8]: https://stackblitz.com
-[9]: https://github.com/webpro-nl/knip/tree/main/packages/knip/fixtures
-[10]: https://github.com/webpro
-[11]: https://github.com/webpro-nl/knip/blob/main/.github/DEVELOPMENT.md
+[9]: https://github.com/webpro-nl/knip/blob/main/.github/DEVELOPMENT.md#tests
+[10]: https://github.com/webpro-nl/knip/tree/main/packages/knip/fixtures
+[11]: https://github.com/webpro
+[12]: https://github.com/webpro-nl/knip/blob/main/.github/DEVELOPMENT.md

package/src/docs/docs/reference/faq.md

@@ -405,10 +405,8 @@ Examples of features that have been requested include:
 - Analyze workspaces in parallel
 - Support Deno
 - Improve internal code structures and accessibility to support contributions
-- One-shot dead code removal (more comprehensive removal of unused variables,
-  duplicate exports, dead code, etc).
 - Replace dependencies for better performance and correctness, such as for shell
-  script parsing, module resolution and globbing with "unignores".
+  script parsing and globbing with "unignores".
 
 These are all interesting ideas, but most increase the API surface area, and all
 require more development efforts and maintenance. Time is limited and

package/src/docs/explanations/comparison-and-migration.md

@@ -95,6 +95,8 @@ Use `knip --exports` to also include class and enum members.
 on a single `tsconfig.json` file (`includes` and `excludes`) and requires no
 configuration. It removes the `export` keyword or the whole export declaration.
 
+**Project status**: The project is archived and recommends Knip.
+
 ## Related projects
 
 Additional alternative and related projects include:

package/src/docs/explanations/plugins.md

@@ -73,7 +73,7 @@ export default defineConfig({
 });
 ```
 
-The Vitest plugin reads this configuration and return two dependencies:
+The Vitest plugin reads this configuration and returns two dependencies:
 
 - `@vitest/coverage-istanbul`
 - `vitest-environment-happy-dom`
@@ -108,7 +108,7 @@ configured.
 
 :::tip[Plugins result in less configuration]
 
-Plugins uses entry file patterns as defined in the configuration files of these
+Plugins uses entry file patterns as defined in your configuration file of these
 tools. So you don't need to repeat this in your Knip configuration.
 
 :::
@@ -242,7 +242,8 @@ dependency.
 
 :::tip[Summary]
 
-Plugins can find additional entry files when parsing config files.
+In your config files, plugins can find additional entry files and also other
+config files recursively.
 
 :::
 
@@ -283,6 +284,14 @@ automatically added as `entry` files for Knip to **statically** resolve the
 
 Additionally, `./setup-tests.ts` will be added as an `entry` file.
 
+:::note
+
+When plugins dynamically load configuration files, conditional dependencies may
+not be detected if the condition evaluates differently during analysis. See
+[conditional or dynamic dependencies][9] for details and workarounds.
+
+:::
+
 ## Command-Line Arguments
 
 Plugins may define the arguments where Knip should look for entry files,
@@ -293,7 +302,7 @@ node --loader tsx scripts/deploy.ts
 playwright test -c playwright.web.config.ts
 ```
 
-Please see [script parser][9] for more details.
+Please see [script parser][10] for more details.
 
 ## Summary
 
@@ -309,11 +318,12 @@ Plugins are configured with two distinct types of files:
 :::
 
 [1]: ../reference/plugins.md
-[2]: ../guides/writing-a-plugin.md
+[2]: ../writing-a-plugin/index.md
 [3]: #configuration-files
 [4]: #entry-files
 [5]: #command-line-arguments
 [6]: ./entry-files.md
 [7]: ../reference/plugins/eslint.md
 [8]: ../reference/plugins/vitest.md
-[9]: ../features/script-parser.md
+[9]: ../guides/handling-issues.mdx#conditional-or-dynamic-dependencies
+[10]: ../features/script-parser.md

package/src/docs/features/auto-fix.mdx

@@ -9,13 +9,13 @@ Run Knip as you normally would, and if the report looks good then run it again
 with the `--fix` flag to let Knip automatically apply fixes. It fixes the
 following [issue types][1]:
 
-- Remove `export` keyword for unused exports and exported types
+- Remove `export` keyword for unused exports, re-exports, and exported types
 - Remove `export default` keywords for unused default exports
-- Remove exports, re-exports and exported types
 - Remove unused enum members
 - Remove unused class members (disabled by default)
 - Remove unused `dependencies` and `devDependencies` from `package.json`
 - Remove unused files
+- Remove unused catalog entries
 
 :::caution
 
@@ -91,9 +91,9 @@ configuration in your project.
 
 ### 2. Unused variables
 
-Use a tool like ESLint or Biome to find and remove unused variables inside
-files. Even better, try [remove-unused-vars][3] to remove unused variables
-within files.
+Use a tool like ESLint or Biome to find and remove unused imports and variables
+inside files. Even better, try [remove-unused-vars][3] to remove unused
+variables within files.
 
 This may result in more deleted code, and Knip may then find more unused code.
 Rinse and repeat!
@@ -316,6 +316,20 @@ component are unused and will remove those.
 
 Note that [`classMembers` aren't included by default][4].
 
+### Catalog entries
+
+Unused [catalog][5] entries are removed from `pnpm-workspace.yaml`:
+
+```diff title="pnpm-workspace.yaml"
+ packages:
+   - 'packages/*'
+ catalog:
+   react: ^18.0.0
+-  unused-package: ^1.0.0
+```
+
+Catalogs in `package.json` are supported as well.
+
 ## What's not included
 
 Operations that auto-fix does not (yet) perform and why:
@@ -331,3 +345,4 @@ Operations that auto-fix does not (yet) perform and why:
 [2]: https://github.com/JoshuaKGoldberg/formatly
 [3]: https://github.com/webpro-nl/remove-unused-vars
 [4]: ../guides/handling-issues.mdx#class-members
+[5]: https://pnpm.io/catalogs

package/src/docs/features/monorepos-and-workspaces.md

@@ -100,16 +100,31 @@ The following options are available inside workspace configurations:
 Use `--debug` for verbose output and see the workspaces Knip includes, their
 configurations, enabled plugins, glob options and resolved files.
 
-## Lint a single workspace
+## Filter workspaces
 
-Use the `--workspace` (or `-W`) argument to focus on a single workspace (and let
-Knip run faster). Example:
+Use the `--workspace` (or `-W`) argument to select one or more workspaces:
 
 ```sh
 knip --workspace packages/my-lib
 ```
 
-This will include the target workspace, but also ancestor and dependent
+The filter supports multiple formats:
+
+```sh
+knip --workspace @myorg/my-lib     # Package name
+knip --workspace '@myorg/*'        # Package name glob
+knip --workspace packages/my-lib   # Directory path
+knip --workspace './apps/*'        # Directory glob
+```
+
+Combine selectors to include or exclude workspaces:
+
+```sh
+knip --workspace @myorg/* --workspace '!@myorg/legacy'
+knip --workspace './apps/*' --workspace '@shared/utils'
+```
+
+This will include the target workspace(s), but also ancestor and dependent
 workspaces. For two reasons:
 
 - Ancestor workspaces may list dependencies in `package.json` the linted

package/src/docs/features/production-mode.md

@@ -37,7 +37,7 @@ Here's what's included in production mode:
 - Only `entry` and `project` patterns suffixed with `!`
 - Only production `entry` file patterns exported by plugins (such as Next.js and
   Remix)
-- Only the `start` and `postinstall` scripts
+- Only the `start` script (of `package.json#scripts`)
 - Ignore exports with the [`@internal` tag][1]
 
 :::note

package/src/docs/features/reporters.md

@@ -79,16 +79,18 @@ The keys match the [reported issue types][6]. Example usage:
 knip --reporter json
 ```
 
-### Github Actions
-
-TODO
+### GitHub Actions
 
+Use the GitHub Actions reporter in a workflow for annotations in pull requests.
 Example usage:
 
 ```sh
 knip --reporter github-actions
 ```
 
+Changed files in pull requests will now contain inline annotations for lint
+findings.
+
 ### Markdown
 
 The built-in `markdown` reporter output is meant to be saved to a Markdown file.
@@ -138,8 +140,8 @@ dangling.js
 <summary>Unused dependencies (2)</summary>
 
 ```
-unused-dep     package.json
-my-package     package.json
+my-package     package.json:17:5
+unused-dep     package.json:20:5
 ```
 
 </details>
@@ -162,8 +164,8 @@ dangling.js
   <summary>Unused dependencies (2)</summary>
 
 ```
-unused-dep     package.json
-my-package     package.json
+my-package     package.json:17:5
+unused-dep     package.json:20:5
 ```
 
 </details>

package/src/docs/guides/configuring-project-files.md

@@ -11,7 +11,7 @@ Knip faster:
 - Start with defaults. Only add targeted `entry` overrides when needed.
 - Use `project` patterns (with negations) to define the scope for Knip.
 - Use production mode to exclude tests and other non-production files.
-- Use `ignore` only to suppress issues in specific files. It does not exclude
+- Use `ignore` only to suppress issues in specific files; it does not exclude
   files from analysis.
 
 Let's dive in and expand on all of these.
@@ -41,7 +41,7 @@ and adjust `project` to fit your codebase.
 Use negated `project` patterns to precisely include/exclude files for unused
 files detection.
 
-Use `ignore` to suppress issues in matching files; it does not remove those
+Use `ignore*` to suppress specific issues in matching files; it does not exclude
 files from analysis.
 
 :::
@@ -87,12 +87,12 @@ positives)? Use negated `project` patterns:
 }
 ```
 
-Why is this better:
+Why this is better:
 
-- `project` defines "what belongs to the codebase" so build outputs are not part
-  of the analysis and don't appear in unused file detection at all
+- `project` defines what belongs to the codebase, so build outputs are excluded
+  from analysis and unused file detection
 - `ignore` is for the few files that should be analyzed but contain exceptions
-- increases performance by analyzing only source files
+- Improves performance by analyzing fewer files
 
 ## Ignore issues in specific files
 
@@ -127,8 +127,8 @@ instead.
 }
 ```
 
-Why not: `ignore` only hides issues from the report; it does not exclude files
-from analysis.
+Why not: `ignore` hides issues from the report; it does not exclude files from
+analysis.
 
 ❌   Also don't do this:
 
@@ -138,8 +138,8 @@ from analysis.
 }
 ```
 
-Why not: plugins for test frameworks add test file as `entry` files, you can't
-and shouldn't override that globally.
+Why not: plugins add test files as `entry` files; you can't and shouldn't
+override that globally.
 
 ❌   Or this:
 
@@ -149,8 +149,8 @@ and shouldn't override that globally.
 }
 ```
 
-Why not: `project` is used for unused file detection. Negating test files here
-is ineffective, because they're `entry` files.
+Why not: `project` is for unused file detection; negating test files is
+ineffective because they are `entry` files.
 
 ✅   Do this instead:
 
@@ -200,6 +200,6 @@ automatically added as well.
 
 [1]: ../typescript/unused-exports.md
 [2]: ../explanations/entry-files.md
-[3]: ../reference/configuration#ignoreexportsusedinfile
+[3]: ../reference/configuration.md#ignoreexportsusedinfile
 [4]: ../features/production-mode.md
 [5]: ../explanations/plugins.md#entry-files

package/src/docs/guides/contributing.md

@@ -20,5 +20,5 @@ contributes to that goal is welcome!
 [1]: https://github.com/webpro-nl/knip
 [2]: ./issue-reproduction.md
 [3]: https://github.com/webpro-nl/knip/blob/main/.github/CONTRIBUTING.md
-[4]: ./writing-a-plugin.md
+[4]: ../writing-a-plugin/index.md
 [5]: https://github.com/webpro-nl/knip/blob/main/.github/DEVELOPMENT.md