@knip/mcp 0.0.12 → 0.0.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.12",
+  "version": "0.0.14",
   "description": "Knip MCP Server",
   "type": "module",
   "bin": {
@@ -26,9 +26,9 @@
   "author": "Lars Kappert <lars@webpro.nl>",
   "license": "ISC",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.24.3",
+    "@modelcontextprotocol/sdk": "^1.25.1",
     "zod": "^4.1.11",
-    "knip": "^5.77.4"
+    "knip": "^5.80.0"
   },
   "engines": {
     "node": ">=18.18.0"

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

@@ -7,32 +7,31 @@ 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].
-
-**EDIT:** Or find [Knip on the Open VSX Registry][6].
+Find [Knip on the VS Code Marketplace][6] and find [Knip in the Open VSX
+Registry][7].
 
 ## MCP Server
 
@@ -41,7 +40,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][8] separately and built into the VS Code
 Extension.
 
 ## Language Server
@@ -53,25 +52,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][9]
 
 ## 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][10]
+  - [Circular Dependencies][11]
+  - [Conflicts][12]
+  - [Branching][13]
+- [VS Code Extension Settings][14]
 
 ### Lint Findings
 
-![Lint Findings][14]
+![Lint Findings][15]
 
 ### Imports & Exports
 
-![hover][15]
+![hover][16]
 
 ### Contention
 
@@ -83,7 +82,7 @@ branched/diamond-shaped import chains.
 
 If an import is part of a circular dependency, Knip will display:
 
-![Circular Dependencies][16]
+![Circular Dependencies][17]
 
 #### Conflicts
 
@@ -91,7 +90,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][18]
 
 #### Branching
 
@@ -99,29 +98,30 @@ 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][19]
 
 ### VS Code Extension Settings
 
-![VS Code Extension Settings][19]
+![VS Code Extension Settings][20]
 
 [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]: https://marketplace.visualstudio.com/items?itemName=webpro.vscode-knip
+[7]: https://open-vsx.org/extension/webpro/vscode-knip
+[8]: https://www.npmjs.com/package/@knip/mcp
+[9]:
   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
+[10]: #contention
+[11]: #circular-dependencies
+[12]: #conflicts
+[13]: #branching
+[14]: #vs-code-extension-settings
+[15]: /screenshots/editors-and-agents/diagnostics.webp
+[16]: /screenshots/editors-and-agents/imports-exports.webp
+[17]: /screenshots/editors-and-agents/circular-dependency.webp
+[18]: /screenshots/editors-and-agents/conflict.webp
+[19]: /screenshots/editors-and-agents/branch.webp
+[20]: /screenshots/editors-and-agents/vscode-extension-settings.webp

package/src/docs/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/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/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/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:
 

package/src/docs/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