@knip/mcp 0.0.16 → 0.0.17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.16",
+  "version": "0.0.17",
   "description": "Knip MCP Server",
   "type": "module",
   "bin": {
@@ -28,7 +28,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.25.1",
     "zod": "^4.1.11",
-    "knip": "^5.81.0"
+    "knip": "^5.82.0"
   },
   "engines": {
     "node": ">=18.18.0"

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

@@ -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/docs/reference/known-issues.md

@@ -23,7 +23,10 @@ the cause of the issue with more details.
 Potential workarounds:
 
 - [Set path aliases][2] for "Cannot find module" errors
-- Set missing environment variable(s)
+- Set missing environment variable(s), potential solutions:
+  - Use a helper package like [dotenvx][3]
+  - `KEY=VAL knip`
+  - `node --env-file .env $(which knip)`
 - Disable loading the file by overriding the default `config` for that plugin.
   - Example: `vite: { config: [] }`
   - In a monorepo, be more specific like so:
@@ -58,8 +61,8 @@ Potential workarounds:
 - Rewrite the import in the configuration file to a relative import.
 - Inject support with a module like `tsx`: `NODE_OPTIONS="--import tsx" knip`
 - Or `tsconfig-paths`: `NODE_OPTIONS="--import tsconfig-paths/register.js" knip`
-- Use Bun with [knip-bun][3].
-- See [exceptions from config files][4] for more potential workarounds.
+- Use Bun with [knip-bun][4].
+- See [exceptions from config files][5] for more potential workarounds.
 
 ## Nx Daemon
 
@@ -69,7 +72,7 @@ In Nx projects you might encounter this error:
 NX   Daemon process terminated and closed the connection
 ```
 
-The solution is to [disable the Nx Daemon][5]:
+The solution is to [disable the Nx Daemon][6]:
 
 ```sh
 NX_DAEMON=false knip
@@ -77,6 +80,7 @@ NX_DAEMON=false knip
 
 [1]: ../guides/handling-issues.mdx
 [2]: #path-aliases-in-config-files
-[3]: ./cli.md#knip-bun
-[4]: #exceptions-from-config-files
-[5]: https://nx.dev/concepts/nx-daemon#turning-it-off
+[3]: https://dotenvx.com/
+[4]: ./cli.md#knip-bun
+[5]: #exceptions-from-config-files
+[6]: https://nx.dev/concepts/nx-daemon#turning-it-off

package/src/docs/docs/reference/related-tooling.md

@@ -4,10 +4,10 @@ title: Related Tooling
 
 This is an overview of related tooling for features Knip does not support.
 
-## Unused variables
+## Unused imports & variables
 
-Knip doesn't look for unused variables within a file. The focus is on exported
-and imported values and types across files.
+Knip doesn't look for unused imports and variables within a file. The focus is
+on exported values and types across files.
 
 Use [ESLint][1], [Biome][2] or [oxlint][3] to find unused variables within
 files.

package/src/docs/docs/typescript/unused-exports.md

@@ -68,7 +68,7 @@ to easily navigate around.
 
 ## How is Knip different from ESLint for finding unused exports?
 
-While linters like ESLint can find unused variables and imports within
+While linters like ESLint can find unused imports and variables within
 individual files, Knip analyzes the entire project to determine which exports
 are actually unused. By building [a comprehensive module graph][7], Knip
 identifies exports that are not imported or used anywhere in the codebase. This