@knip/mcp 0.0.12 → 0.0.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.12",
+  "version": "0.0.13",
   "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.79.0"
   },
   "engines": {
     "node": ">=18.18.0"

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`
@@ -283,6 +283,12 @@ 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][10] for details and workarounds.
+
+:::
+
 ## Command-Line Arguments
 
 Plugins may define the arguments where Knip should look for entry files,
@@ -317,3 +323,4 @@ Plugins are configured with two distinct types of files:
 [7]: ../reference/plugins/eslint.md
 [8]: ../reference/plugins/vitest.md
 [9]: ../features/script-parser.md
+[10]: ../guides/handling-issues.mdx#conditional-or-dynamic-dependencies

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,8 +41,8 @@ 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
-files from analysis.
+Use `ignore` to suppress 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/handling-issues.mdx

@@ -6,16 +6,11 @@ sidebar:
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 
-A long report can be frustrating. The list may contain false positives, but also
-tons of useful information. To get the most value out of Knip, it may require
-some initial configuration.
+Issues reported by Knip may contain false positives, but also tons of useful
+information. Getting the most out of Knip may require some configuration.
 
-This guide helps you deal with false positives to find solutions and create the
-perfect report, with minimal configuration that will keep your project tidy.
-
-If you start out using Knip in a large project and have a long report, it makes
-sense to go over the issue types one by one. For instance, reducing the number
-of unused files will also reduce the number of unused dependencies.
+Go over the issue types one by one. For instance, reducing the number of unused
+files will also reduce the number of unused dependencies.
 
 1. [Unused files][1]
 2. [Unused dependencies][2]
@@ -124,8 +119,8 @@ Entry files referenced in HTML files (e.g. `<script src="production.js">`).
 compiler to extract and resolve the value of `<script src>` elements.
 
 Knip has support for some popular framework formats through [compilers][19], and
-additional compilers can be added for for any file type. The recommended
-solution is usually to add the file as shown in each example as an `entry` file.
+additional compilers can be added for any file type. The recommended solution is
+usually to add the file as shown in each example as an `entry` file.
 
 ### Missing plugin
 
@@ -253,6 +248,7 @@ The most common causes for unused dependencies include:
 - [Missing or incomplete plugins][27]
 - [Unrecognized references][28]
 - [Type Definition Packages][29]
+- [Dependencies named after Node.js builtins][30]
 
 Use `--dependencies` to [filter the report][15] and focus only on issues related
 to dependencies:
@@ -264,8 +260,8 @@ knip --dependencies
 :::caution[Monorepo]
 
 In a monorepo, a dependency is unused in the root workspace's `package.json` if
-it's also listed in an descendent workspace, and referenced only in the
-descendent workspace.
+it's also listed in a descendant workspace, and referenced only in the
+descendant workspace.
 
 :::
 
@@ -288,7 +284,54 @@ so it's a false positive and incorrectly reported as unused.
 like a plugin could solve it, a last resort is to use [ignoreDependencies][22].
 
 If a binary (or "executable") is referenced you'll want to use `ignoreBinaries`
-instead. See [unlisted binaries][30].
+instead. See [unlisted binaries][31].
+
+### Dependencies named after Node.js builtins
+
+Some packages have the same name as a Node.js builtin (for instance `buffer` or
+`process`).
+
+**Solution**: if Knip reports such a dependency as unused, add it to
+[ignoreDependencies][22].
+
+#### Conditional or dynamic dependencies
+
+Dependencies added conditionally in configuration files may not be detected by
+Knip. This happens because Knip loads and executes config files, and conditional
+logic may evaluate differently during analysis.
+
+For example, this Playwright configuration conditionally adds a reporter:
+
+```ts title="playwright.config.ts"
+import { defineConfig } from '@playwright/test';
+
+const reporters: any[] = [['list']];
+if (process.env.REPORT_PORTAL_ENABLED) {
+  reporters.push(['@reportportal/agent-js-playwright', config]);
+}
+
+export default defineConfig({
+  reporter: reporters,
+});
+```
+
+If `process.env.REPORT_PORTAL_ENABLED` evaluates to `false` when Knip runs, the
+`@reportportal/agent-js-playwright` dependency won't be detected and may be
+reported as unused.
+
+This limitation exists because Knip executes configuration files to parse their exported value.
+While Knip can parse configuration files statically using AST (Abstract
+Syntax Tree) analysis, this approach becomes complex very quickly and most of
+the time it is easier to use the [`ignoreDependencies`][22] configuration option
+for conditionals.
+
+```json title="knip.json"
+{
+  "ignoreDependencies": ["@reportportal/agent-js-playwright"]
+}
+```
+
+This pattern can be applied to any plugin that loads configuration files.
 
 ### Type Definition Packages
 
@@ -349,7 +392,7 @@ reported as an unlisted binary as there is no package that contains it.
 
 Binaries that are installed on the OS already and thus likely not meant to be
 installed from npm are not reported as unlisted (details: [list of ignored
-binaries in source][31]).
+binaries in source][32]).
 
 #### Missing binaries
 
@@ -359,7 +402,7 @@ either the way your package manager installs dependencies and binaries, or by
 not running Knip from the root of the repository.
 
 **Solution**: run Knip from the project root. If needed, [lint workspaces
-individually][32].
+individually][33].
 
 Sometimes binaries and how they're reported can be a bit confusing. See this
 example:
@@ -395,10 +438,10 @@ or consider the binary and package(s) referenced, respectively.
 Knip may ignore or be unable to resolve an import specifier or dependency
 references. The most common causes for unresolved imports:
 
-- [Template strings][33]
+- [Template strings][34]
 - [Extensionless imports][28]
-- [Unrecognized path aliases][34]
-- [External aliased imports][35]
+- [Unrecognized path aliases][35]
+- [External aliased imports][36]
 
 ### Template strings
 
@@ -435,11 +478,11 @@ similar to how standard ES Modules specifies file extensions are necessary.
 
 ### Unrecognized path aliases
 
-Knip considers TS config path aliases and [paths configured in knip.json][36],
+Knip considers TS config path aliases and [paths configured in knip.json][37],
 but not those in e.g. Webpack or Vite configurations.
 
-**Solution**: configure [paths][36] or try relative imports. Otherwise, use
-[`ignoreUnresolved`][37] as a last resort.
+**Solution**: configure [paths][37] or try relative imports. Otherwise, use
+[`ignoreUnresolved`][38] as a last resort.
 
 ### External aliased imports
 
@@ -458,9 +501,9 @@ option][13] to tell Knip where to find the icon types:
 ```
 
 Where `[framework]` is the name of the framework you're using (see [available
-types][38]).
+types][39]).
 
-**Solution**: try [--include-libs][39] or configure [paths][36].
+**Solution**: try [--include-libs][40] or configure [paths][37].
 
 ## Unused exports
 
@@ -468,8 +511,8 @@ By default, Knip does not report unused exports of `entry` files.
 
 The most common causes for unused exports include:
 
-- [Namespace enumerations][40]
-- [External libraries][39]
+- [Namespace enumerations][41]
+- [External libraries][40]
 
 Use the `--exports` flag to [filter][15] and focus only on issues related to
 exports:
@@ -478,7 +521,7 @@ exports:
 knip --exports
 ```
 
-Use [includeEntryExports][41] to report unused exports of entry files as well.
+Use [includeEntryExports][42] to report unused exports of entry files as well.
 This can be set per workspace.
 
 ### Namespace enumerations
@@ -490,7 +533,7 @@ are then **not** reported.
 **Solution**: if all exports on imported namespaces should be considered
 individually, include the `nsExports` issue type to disable the heuristic.
 
-See [namespace imports][42] to see all related patterns.
+See [namespace imports][43] to see all related patterns.
 
 ### External libraries
 
@@ -510,6 +553,7 @@ non-standard consumption of your exports? Here's an example:
       resolveComponent: components => components.Orange,
     });
     ```
+
   </TabItem>
 
   <TabItem label="components.js">
@@ -526,22 +570,22 @@ Knip does not include external type definitions by default so it won't see the
 export being referenced.
 
 **Solution**: include the type definitions of external libraries with the
-[--include-libs][43] flag:
+[--include-libs][44] flag:
 
 ```shell
 knip --include-libs
 ```
 
 This comes at a performance and memory penalty, but should give better results
-if you need it. This flag is implied when [classMembers][44] are included (that
+if you need it. This flag is implied when [classMembers][45] are included (that
 feature comes with roughly the same performance penalty).
 
 ### Exclude exports from the report
 
 To exclude false positives from the report, there are a few options:
 
-- [Ignore exports used in file][45] for exports used internally.
-- Individual exports can be [tagged using JSDoc syntax][46].
+- [Ignore exports used in file][46] for exports used internally.
+- Individual exports can be [tagged using JSDoc syntax][47].
 - Have the export in an entry file:
   - Add the file to the `entry` file patterns array in the configuration.
   - Move the export(s) to an entry file.
@@ -551,7 +595,7 @@ To exclude false positives from the report, there are a few options:
 ### Missing unused exports?
 
 Did you expect certain exports in the report, but are they missing? They might
-be exported from an entry file. In that case, use [--include-entry-exports][41]
+be exported from an entry file. In that case, use [--include-entry-exports][42]
 to make Knip also report unused exports in entry files.
 
 The exports of non-standard extensions like `.astro`, `.mdx`, `.vue` or
@@ -570,10 +614,10 @@ knip --include classMembers
 This option is also available in the Knip configuration file. Note that this
 feature comes at a cost: linting will take more time and more memory.
 
-Individual class members can be [tagged using JSDoc syntax][46].
+Individual class members can be [tagged using JSDoc syntax][47].
 
 Classes exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][41] to make Knip also report members of unused exports
+[--include-entry-exports][42] to make Knip also report members of unused exports
 in entry files.
 
 ### Enum members
@@ -585,16 +629,16 @@ Reporting such members can be disabled:
 knip --exclude enumMembers
 ```
 
-Individual enum members can be [tagged using JSDoc syntax][46].
+Individual enum members can be [tagged using JSDoc syntax][47].
 
 Enums exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][41] to make Knip also report members of unused exports
+[--include-entry-exports][42] to make Knip also report members of unused exports
 in entry files.
 
 ## Feedback or false positives?
 
 If you believe Knip incorrectly reports something as unused (i.e. there's a
-false positive), feel free to create a [minimal reproduction][47] and open an
+false positive), feel free to create a [minimal reproduction][48] and open an
 issue on GitHub. It'll make Knip better for everyone!
 
 [1]: #unused-files
@@ -621,26 +665,29 @@ issue on GitHub. It'll make Knip better for everyone!
 [22]: ../reference/configuration.md#ignoredependencies
 [23]: ../explanations/plugins.md#entry-files
 [24]: ../explanations/entry-files.md#plugins
-[25]: ../reference/faq.md#why-cant-i-use-path-aliases-to-reference-other-workspaces
+[25]:
+  ../reference/faq.md#why-cant-i-use-path-aliases-to-reference-other-workspaces
 [26]: ../features/integrated-monorepos.md
 [27]: #missing-or-incomplete-plugin
 [28]: #unrecognized-reference
 [29]: #type-definition-packages
-[30]: #unlisted-binaries
-[31]: https://github.com/webpro-nl/knip/blob/b70958a58ea255ee7a7831e404786da807ca93d7/packages/knip/src/constants.ts#L37-L139
-[32]: ../features/monorepos-and-workspaces.md#lint-a-single-workspace
-[33]: #template-strings
-[34]: #unrecognized-path-aliases
-[35]: #external-aliased-imports
-[36]: ../reference/configuration.md#paths
-[37]: ../reference/configuration.md#ignoreunresolved
-[38]: #build-artifacts-and-ignored-files
-[39]: #external-libraries
-[40]: #namespace-enumerations
-[41]: ../reference/configuration.md#includeentryexports
-[42]: ../guides/namespace-imports.md
-[43]: ../reference/cli#--include-libs
-[44]: #class-members
-[45]: ../reference/configuration.md#ignoreexportsusedinfile
-[46]: ../reference/jsdoc-tsdoc-tags.md
-[47]: ../guides/issue-reproduction
+[30]: #dependencies-named-after-nodejs-builtins
+[31]: #unlisted-binaries
+[32]:
+  https://github.com/webpro-nl/knip/blob/b70958a58ea255ee7a7831e404786da807ca93d7/packages/knip/src/constants.ts#L37-L139
+[33]: ../features/monorepos-and-workspaces.md#lint-a-single-workspace
+[34]: #template-strings
+[35]: #unrecognized-path-aliases
+[36]: #external-aliased-imports
+[37]: ../reference/configuration.md#paths
+[38]: ../reference/configuration.md#ignoreunresolved
+[39]: #build-artifacts-and-ignored-files
+[40]: #external-libraries
+[41]: #namespace-enumerations
+[42]: ../reference/configuration.md#includeentryexports
+[43]: ../guides/namespace-imports.md
+[44]: ../reference/cli#--include-libs
+[45]: #class-members
+[46]: ../reference/configuration.md#ignoreexportsusedinfile
+[47]: ../reference/jsdoc-tsdoc-tags.md
+[48]: ../guides/issue-reproduction

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

package/src/docs/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/docs/reference/configuration.md

@@ -198,17 +198,23 @@ Exit with non-zero code (1) if there are any configuration hints.
 
 :::tip
 
-Please read [configuring project files][9] before using the `ignore` option,
-because in most cases you'll want to fine‑tune `entry` and `project` (or use
-production mode) instead.
+Please read [configuring project files][9] before using the `ignore` option.
 
 :::
 
-Array of glob patterns to ignore issues from matching files. Example:
+Avoid `ignore` patterns. There is almost always a better solution:
+
+- Follow up on configuration hints (if there are any).
+- Fine-tune `entry` and `project` patterns.
+- Use [production mode][10].
+- Other `ignore*` options.
+
+**NOTE**: An exception to the rule: to _temporarily_ report only issues in files
+that match the negated `ignore` pattern:
 
 ```json title="knip.json"
 {
-  "ignore": ["src/generated.ts", "fixtures/**"]
+  "ignore": ["!src/dir/**"]
 }
 ```
 
@@ -271,6 +277,8 @@ export default {
 
 Suffix an item with `!` to enable it only in production mode.
 
+Also see [Unused dependencies][11].
+
 ### `ignoreMembers`
 
 Array of class and enum members to exclude from the report. Regular expressions
@@ -399,7 +407,7 @@ files (`.js` or `.ts`), not in JSON configuration files.
 
 Override built-in compilers or add custom compilers for additional file types.
 
-Also see [Compilers][10].
+Also see [Compilers][12].
 
 [1]: ../reference/dynamic-configuration.mdx
 [2]: ../overview/configuration.md
@@ -410,4 +418,6 @@ Also see [Compilers][10].
 [7]: ../features/rules-and-filters.md#filters
 [8]: ./jsdoc-tsdoc-tags.md
 [9]: ../guides/configuring-project-files.md
-[10]: ../features/compilers.md
+[10]: ../features/production-mode.md
+[11]: ../guides/handling-issues.mdx#unused-dependencies
+[12]: ../features/compilers.md

package/src/docs/docs/reference/known-issues.md

@@ -2,31 +2,45 @@
 title: Known Issues
 ---
 
-This page contains a list of known issues you might run into when using Knip.
+List of known issues and workarounds for exceptions thrown during a Knip run.
+
+See [handling issues][1] to learn more about dealing with lint issues.
 
 ## Exceptions from config files
 
 An exception may be thrown when a Knip plugin loads a JavaScript or TypeScript
-configuration file such as `webpack.config.js` or `vite.config.ts`. Knip may
-load such files differently, in a different environment, or without certain
-environment variables set.
+configuration file such as `webpack.config.js` or `vite.config.ts`:
 
-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. Examples of issues when Knip
-loads configuration files:
+```sh
+$ knip
+Error loading .../vite.config.ts
+```
 
-- Missing environment variable
-- Relative path (e.g. which is sometimes not resolved from correct directory,
-  try `import.meta.dirname` or `__dirname`)
+Knip may load such files differently, in a different environment, with missing
+environment variables, etcetera. Use `--debug` to locate the cause of the issue
+with more details.
 
-As a last resort, the [plugin can be disabled][1].
+Potential workarounds:
+
+- Disable loading the file by overriding the default `config` for that plugin.
+  - Example: `vite: { config: [] }`
+  - In a monorepo, be more specific like so:
+    `workspaces: { "packages/lib": { vite: { config: [] } } }`
+  - If this helps, add the file as an `entry` file for static analysis.
+- Disable the related plugin.
+  - Example: `eslint: false`
+  - In a monorepo, be more specific like so:
+    `workspaces: { "packages/lib": { eslint: false } }`
+  - If this helps, add the file as an `entry` file for static analysis.
+- As a last resort, ignore the workspace: `ignoreWorkspaces: ["packages/lib"]`.
 
 ## Path aliases in config files
 
 Loading the configuration file (e.g. `cypress.config.ts`) for one of Knip's
 plugins may give an error:
 
-```
+```sh
+$ knip
 Analyzing workspace ....
 Error loading .../cypress.config.ts
 Reason: Cannot find module '@alias/name'
@@ -35,15 +49,13 @@ Require stack:
 ```
 
 Some tools (such as Cypress and Jest) support using TypeScript path aliases in
-the configuration file. Jiti does support aliases, but in a different format
-compared to `tsconfig.json#compilerOptions.paths` and `knip.json#paths` (e.g.
-the target values are not arrays).
+the configuration file.
 
 Potential workarounds:
 
 - Rewrite the import in the configuration file to a relative import.
 - Use Bun with [knip-bun][2].
-- [Disable the plugin][1] (not recommended, try the other options first).
+- See [exceptions from config files][3] for more potential workarounds.
 
 ## Nx Daemon
 
@@ -53,12 +65,13 @@ In Nx projects you might encounter this error:
 NX   Daemon process terminated and closed the connection
 ```
 
-The solution is to [disable the Nx Daemon][3]:
+The solution is to [disable the Nx Daemon][4]:
 
 ```sh
 NX_DAEMON=false knip
 ```
 
-[1]: ./configuration.md#plugins
+[1]: ../guides/handling-issues.mdx
 [2]: ./cli.md#knip-bun
-[3]: https://nx.dev/concepts/nx-daemon#turning-it-off
+[3]: #exceptions-from-config-files
+[4]: https://nx.dev/concepts/nx-daemon#turning-it-off

package/src/docs/docs/reference/plugins/bun.md

@@ -8,26 +8,6 @@ sidebar:
 
 This plugin is enabled if `"bun"` is listed in `"dependencies"` or `"devDependencies"` in `package.json`.
 
-## Default configuration
-
-If this plugin is enabled, the following configuration is added automatically:
-
-```json
-{
-  "bun": {
-    "config": [
-      "package.json"
-    ]
-  }
-}
-```
-
-Depending on local configuration, plugins may modify the defaults as shown.
-
-Custom `config` or `entry` options override default values, they are not merged.
-
-See [Plugins](../../explanations/plugins) for more details about plugins and their `entry` and `config` options.
-
 ## Generated from source
 
 This page was generated from the [bun plugin source code](https://github.com/webpro-nl/knip/blob/main/packages/knip/src/plugins/bun/index.ts).

package/src/docs/docs/reference/plugins/lefthook.md

@@ -23,10 +23,10 @@ If this plugin is enabled, the following configuration is added automatically:
   "lefthook": {
     "config": [
       "lefthook.yml",
-      ".git/hooks/prepare-commit-msg",
-      ".git/hooks/commit-msg",
-      ".git/hooks/pre-{applypatch,commit,merge-commit,push,rebase,receive}",
-      ".git/hooks/post-{checkout,commit,merge,rewrite}"
+      "../../../../../.git/hooks/prepare-commit-msg",
+      "../../../../../.git/hooks/commit-msg",
+      "../../../../../.git/hooks/pre-{applypatch,commit,merge-commit,push,rebase,receive}",
+      "../../../../../.git/hooks/post-{checkout,commit,merge,rewrite}"
     ]
   }
 }

package/src/docs/docs/reference/plugins/node.md

@@ -15,8 +15,8 @@ If this plugin is enabled, the following configuration is added automatically:
 ```json
 {
   "node": {
-    "config": [
-      "package.json"
+    "entry": [
+      "server.js"
     ]
   }
 }

package/src/docs/docs/reference/plugins/nx.md

@@ -39,7 +39,7 @@ See [Plugins](../../explanations/plugins) for more details about plugins and the
 
 ## Note
 
-Also see [integrated monorepos](/features/integrated-monorepos).
+Also see [integrated monorepos](/features/integrated-monorepos) and the note regarding internal workspace dependencies.
 
 ## Shell commands
 

package/src/docs/docs/reference/plugins/playwright-ct.md

@@ -18,11 +18,11 @@ If this plugin is enabled, the following configuration is added automatically:
 {
   "playwright-ct": {
     "config": [
-      "playwright-ct.config.{js,ts}",
-      "playwright/index.{js,ts,jsx,tsx}"
+      "playwright-ct.config.{js,ts}"
     ],
     "entry": [
-      "**/*.@(spec|test).?(c|m)[jt]s?(x)"
+      "**/*.@(spec|test).?(c|m)[jt]s?(x)",
+      "playwright/index.{js,ts,jsx,tsx}"
     ]
   }
 }

package/src/docs/docs/reference/plugins/vitepress.md

@@ -0,0 +1,34 @@
+---
+title: VitePress
+sidebar:
+  hidden: true
+---
+
+## Enabled
+
+This plugin is enabled if `"vitepress"` is listed in `"dependencies"` or `"devDependencies"` in `package.json`.
+
+## Default configuration
+
+If this plugin is enabled, the following configuration is added automatically:
+
+```json
+{
+  "vitepress": {
+    "entry": [
+      ".vitepress/config.{js,ts,mjs,mts}",
+      ".vitepress/theme/index.{js,ts,mjs,mts}"
+    ]
+  }
+}
+```
+
+Depending on local configuration, plugins may modify the defaults as shown.
+
+Custom `config` or `entry` options override default values, they are not merged.
+
+See [Plugins](../../explanations/plugins) for more details about plugins and their `entry` and `config` options.
+
+## Generated from source
+
+This page was generated from the [vitepress plugin source code](https://github.com/webpro-nl/knip/blob/main/packages/knip/src/plugins/vitepress/index.ts).

package/src/docs/docs/sponsors.mdx

@@ -8,7 +8,6 @@ import Posts from '../../components/Posts.astro';
 import Projects from '../../components/Projects.astro';
 import SponsorsComponent from '../../components/Sponsors.astro';
 import SponsorsChart from '../../components/SponsorsChart.astro';
-import SponsorsPast from '../../components/SponsorsPast.astro';
 
 :::article{.prose}
 
@@ -41,7 +40,7 @@ one year before that.
 <SponsorsChart />
 
 - The monthly aggregated average over the charted period is $514.
-- The monthly recurring average without one-time payments is $339.
+- The monthly recurring average without one-time payments is $345.
 - GitHub Sponsors is for my GitHub account. This has more repositories, but in
   practice targets mostly Knip (and perhaps some [release-it][5]).
 - [Chart generated][6] using [Venz][7].
@@ -61,5 +60,5 @@ one year before that.
 [3]: https://github.com/sponsors/webpro
 [4]: https://opencollective.com/knip
 [5]: https://github.com/release-it/release-it
-[6]: https://try.venz.dev?type=pivot&lp=tr&br=0&labelX=month&labelY=amount+\($\)&l=GitHub+Sponsors&color=%23fbfbfb&l=Open+Collective&color=%232487ff&label=2023-11&data=9,0&label=2023-12&data=74,0&label=2024-01&data=239,0&label=2024-02&data=489,0&label=2024-03&data=189,0&label=2024-04&data=204,750&label=2024-05&data=304,101&label=2024-06&data=1204,0&label=2024-07&data=204,35&label=2024-08&data=229,25&label=2024-09&data=2729,25&label=2024-10&data=410,45&label=2024-11&data=222,45&label=2024-12&data=222,145&label=2025-01&data=342,145&label=2025-02&data=244,145&label=2025-03&data=222,145&label=2025-04&data=222,145&label=2025-05&data=242,145&label=2025-06&data=247,145&label=2025-07&data=297,145&label=2025-08&data=268,145&label=2025-09&data=350,145&label=2025-10&data=375,145
+[6]: https://try.venz.dev?type=pivot&lp=tr&br=0&labelX=month&labelY=amount+\($\)&l=GitHub+Sponsors&color=%23fbfbfb&l=Open+Collective&color=%232487ff&label=2023-11&data=9,0&label=2023-12&data=74,0&label=2024-01&data=239,0&label=2024-02&data=489,0&label=2024-03&data=189,0&label=2024-04&data=204,750&label=2024-05&data=304,101&label=2024-06&data=1204,0&label=2024-07&data=204,35&label=2024-08&data=229,25&label=2024-09&data=2729,25&label=2024-10&data=410,45&label=2024-11&data=222,45&label=2024-12&data=222,145&label=2025-01&data=342,145&label=2025-02&data=244,145&label=2025-03&data=222,145&label=2025-04&data=222,145&label=2025-05&data=242,145&label=2025-06&data=247,145&label=2025-07&data=297,145&label=2025-08&data=268,145&label=2025-09&data=350,145&label=2025-10&data=375,145&label=2025-11&data=549,145&label=2025-12&data=355,145
 [7]: https://try.venz.dev

package/src/texts.js

@@ -1,24 +1,23 @@
 import { CURATED_RESOURCES } from './curated-resources.js';
 
 export const WORKFLOW = `Workflow:
-1. Read essential documentation resources to understand Knip configuration
+
+1. Read essential documentation resources:
+   - configuring-project-files (must read to configure entry patterns)
+   - plugins-explanation (understand entries added by auto-detected plugins)
+   - handling-issues (comprehensive guide to deal with any reported issue type)
+   - configuration-reference (all knip.json configuration options)
 2. Run analysis (knip-run) to get configuration hints and issues
 3. Address the hints by adjusting knip.json
-4. Repeat steps 2-3 until no hints remain and false positives are minimized
-
-Essential resources:
-- configuring-project-files (must read to configure entry patterns)
-- plugins-explanation (understand entries added by auto-detected plugins)
-- handling-issues (comprehensive guide to deal with any reported issue type)
-- configuration-reference (all knip.json configuration options)
+4. Repeat steps 2-3 until hints are gone and false positives are minimized
 
-For direct "run knip" or "clean up codebase" requests: Always make sure to run this workflow first.
-
-Important (potential next steps after workflow is finished):
-- Before suggesting fixes/solutions, make sure to consult "handling-issues" and "reference/jsdoc-tsdoc-tags"
-- Read "getting-started" and "reference/cli" to install knip and start using Knip from CLI
-- If requested to clean up, consult "features/auto-fix"
-- Knip does not find/fix unused variables/imports within files (use another linter for that)
+Important notes:
+- For prompts like "run knip" or "clean up codebase" or "no more slop": always run workflow to configure Knip first.
+- If you hit errors (not lint issues), consult: known-issues
+- Before suggesting fixes/solutions, consult: handling-issues and reference/jsdoc-tsdoc-tags
+- For cleanup, consult: features/auto-fix
+- To install Knip and start using it from CLI, consult: getting-started and reference/cli
+- Knip does not remove unused imports/variables inside files (use a linter)
 `;
 
 // pkg.contributes.languageModelTools[0].modelDescription
@@ -44,26 +43,17 @@ ${Object.entries(CURATED_RESOURCES)
   .map(([id, doc]) => `- ${id}: ${doc.description}`)
   .join('\n')}
 
-Can also fetch any doc by path (e.g., "reference/cli" or "guides/troubleshooting").
-Use this instead of fetching from knip.dev.`;
+Can also fetch any doc by path (e.g. "reference/cli" or "guides/troubleshooting").
+Use this instead of fetching from https://knip.dev.`;
 
 // pkg.contributes.languageModelTools[1].inputSchema.properties.topic.description
 export const DOC_TOOL_TOPIC_DESCRIPTION =
   'Topic key (e.g. "configuring-project-files") for curated resources, or path (e.g. "explanations/plugins") for all available docs';
 
 export const ERROR_HINT = `For unexpected errors (exit code 2) such as "error loading file":
+
 - Consult docs: known-issues and configuration-reference
-- If no config file exists, create knip.json in root: {"$schema":"https://unpkg.com/knip@5/schema.json"}
-- Damage control for "error loading file":
-  1) First try to disable the related plugin's config file:
-     - E.g. vite: { config: [] }
-     - In a monorepo use e.g. { workspaces: { "packages/lib": { vite: { config: [] } } } }
-     - If this succeeds, add the file as a regular entry point
-  2) Then try to disable the related plugin:
-     - E.g. vite: false
-     - In a monorepo use e.g. { workspaces: { "packages/lib": { vite: false } } }
-     - If this succeeds, add the file as a regular entry point
-  3) As a last resort, ignore the workspace: ignoreWorkspaces: ["packages/lib"]
+- If no config file exists, create knip.json in the project root
 - Run knip again`;
 
 export const CONFIG_REVIEW_HINT = `Review the existing configuration for potential improvements:
@@ -71,7 +61,7 @@ export const CONFIG_REVIEW_HINT = `Review the existing configuration for potenti
 - Never use "ignore" patterns (hides real issues!), always prefer specific solutions, other ignore* options are allowed
 - Many unused exported types? Add: ignoreExportsUsedInFile: { interface: true, type: true } (prefer this over other ignore* options)
 - Remove ignore patterns that don't match any files
-- Redundant ignore patterns: Knip respects .gitignore by default (node_modules, dist, build, .git)
+- Remove redundant ignore patterns: Knip respects .gitignore (node_modules, dist, build, .git)
 - Remove entry patterns covered by config defaults and auto-detected plugins
 - Config files (e.g. vite.config.ts) showing as unused? Enable/disable the plugin explicitly
 - Dependencies matching Node.js builtins: add to ignoreDependencies (e.g. buffer, process)