@knip/mcp 0.0.17 → 0.0.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.17",
+  "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.82.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

@@ -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
 
@@ -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/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/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>