@knip/mcp 0.0.21 → 0.0.23

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.21",
+  "version": "0.0.23",
   "description": "Knip MCP Server",
   "keywords": [
     "knip",
@@ -28,10 +28,10 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.27.1",
     "zod": "^4.1.11",
-    "knip": "^5.87.0"
+    "knip": "^6.0.0"
   },
   "engines": {
-    "node": ">=18.18.0"
+    "node": "^20.19.0 || >=22.12.0"
   },
   "scripts": {
     "release": "release-it -c ../../.release-it.json"

package/src/docs/docs/blog/brief-history.md

@@ -2,7 +2,7 @@
 title: A Brief History Of Knip
 date: 2023-10-15
 sidebar:
-  order: 7
+  order: 8
 ---
 
 _Published: 2023-10-15_
@@ -21,8 +21,7 @@ just for you!
 - 2023-03-22: [Knip v2][5] saw a full rewrite of the TypeScript backend.
 - 2023-10-15: [Introduction of Knip v3][6].
 
-[1]:
-  https://github.com/webpro-nl/knip/commit/9589dfe22608da7d89f2613383da6db5826226d2
+[1]: https://github.com/webpro-nl/knip/commit/9589dfe22608da7d89f2613383da6db5826226d2
 [2]: https://github.com/webpro-nl/knip/tree/0.1.2
 [3]: https://github.com/webpro-nl/knip/releases/tag/1.0.0-alpha.0
 [4]: https://github.com/webpro-nl/knip/tree/1.0.0

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

@@ -2,7 +2,7 @@
 title: Knip for Editors & Agents
 date: 2025-12-17
 sidebar:
-  order: 1
+  order: 2
 ---
 
 _Published: 2025-12-17_
@@ -116,8 +116,7 @@ barrel files. Knip warns:
 [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
+[10]: https://github.com/webpro-nl/knip/blob/main/packages/language-server/README.md
 [11]: #contention
 [12]: #circular-dependencies
 [13]: #conflicts

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

@@ -2,7 +2,7 @@
 title: Announcing Knip v3
 date: 2023-10-15
 sidebar:
-  order: 8
+  order: 9
 ---
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';

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

@@ -2,7 +2,7 @@
 title: Announcing Knip v4
 date: 2024-01-16
 sidebar:
-  order: 5
+  order: 6
 ---
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';

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

@@ -2,7 +2,7 @@
 title: Announcing Knip v5
 date: 2024-02-10
 sidebar:
-  order: 4
+  order: 5
 ---
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';

package/src/docs/docs/blog/knip-v6.md

@@ -0,0 +1,145 @@
+---
+title: Announcing Knip v6
+date: 2026-03-20
+sidebar:
+  order: 1
+---
+
+_Published: 2026-03-20_
+
+## Knip v6 is out!
+
+This release is all about replacing the TypeScript backend entirely with
+`oxc-parser` and `oxc-resolver`, and making Knip a whole lot faster!
+
+## From TypeScript to oxc
+
+Two years ago, the ["slim down to speed up"][1] and [Knip v4][2] work removed a
+lot of overhead around TypeScript programs, made serialization and caching
+practical, and improved memory efficiency a lot. But there was still a ceiling:
+parsing and module resolution still depended on TypeScript APIs designed for
+IDEs and language servers — not for the kind of single-pass static analysis Knip
+does.
+
+Starting today, Knip v6 parses your source files with [oxc-parser][3]. This is
+more than just a parser swap for the sake of using the latest 'n greatest.
+
+Knip has always been designed to parse each file only once, but the TypeScript
+backend carried the overhead of wiring up an entire program along with the
+typechecker. That's useful for IDEs keeping symbols connected, but much less so
+when you only need to traverse an AST once to collect imports and exports.
+The TypeScript backend made the setup as a whole harder and slower than it
+needed to be, especially to keep large monorepos in check.
+
+Now with TypeScript itself Go-ing places, replacing that backend was only a
+matter of time.
+
+Unsurprisingly, the search didn't take long: `oxc-parser` offers everything we
+need and its (experimental) raw transfer is crazy fast. Massive props to
+[overlookmotel][4], [Boshen][5] and all contributors for all the work on
+[the oxc suite][6]!
+
+## Performance tuning
+
+Next to this major refactor, I've been having a ball tuning Knip's performance
+further. One thing to highlight here is that a few more plugins have been
+refactored to statically analyze configuration files directly, as opposed to
+actually importing them (including transitive dependencies...). This includes
+the ESLint ("flat config"), tsdown and tsup plugins.
+
+## The numbers
+
+Comparing v5 and v6 in some projects using Knip, all boosts are in the **2-4x** range:
+
+[![venz-chart][8]][7]
+
+Trust me, I could look at this chart all day long! The same numbers in a table:
+
+| Project          | v5.88.0 | v6.0.0 |
+| ---------------- | ------: | -----: |
+| [astro][9]       |    4.0s |   2.0s |
+| [query][10]      |    3.8s |   1.7s |
+| [rolldown][11]   |    3.7s |   1.7s |
+| [sentry][12]     |   11.0s |   4.0s |
+| [TypeScript][13] |    3.7s |   0.9s |
+
+## What's new
+
+- Did I already mention Knip got 2-4x faster?
+- Support for TS namespaces (and modules), new issue type `namespaceMembers`:
+
+```ts
+export namespace MyNamespace {
+  export const myName = 'knip'; // we were ignored in v5,
+  export type MyType = string; // yet in v6 we are included
+}
+```
+
+## Breaking changes
+
+Granted, most of you won't even notice. Here's the list:
+
+- Dropped support for Node.js v18 → Knip v6 requires Node.js v20.19.0 or newer
+- Dropped issue type `classMembers`
+- Dropped `--include-libs` → this is now the default and only behavior
+- Dropped `--isolate-workspaces` → this is now the default and only behavior
+- Dropped `--experimental-tags` → use [`--tags`][14]
+- In [reporter functions][15], `issues.files` is consistent with other issue shapes. Removed `issues._files`.
+- In the [JSON reporter][16], issues are consistently arrays for any issue type. Removed root `files`.
+
+## Editor Extensions
+
+[Editor extensions][17] benefit from the core upgrades, for being faster and more
+memory-efficient. Regardless of new extension releases, the local version of
+Knip will be detected and used. Upgrade `knip` in your dependencies when you're
+ready.
+
+## What about classMembers?
+
+I feel you. Even Knip itself was using it. Until today.
+
+The problem is that the implementation relies on the JS-based `ts.LanguageService`
+API that exposes the `findReferences` method. TypeScript v6 is the last JS-based
+release, and TypeScript v7 is a full rewrite in Go. I am left wondering if it
+ever will be feasible and practical to build such features using primitives
+(i.e. not via LSP) in a JS-based CLI (references: [microsoft/typescript-go#455][18],
+[@typescript/api][19]). Knip was already pretty unique for even trying this in
+a CLI tool.
+
+Not that many projects seem to be using it either:
+[github.com search for "classMembers path\:knip.json"][20].
+
+If your project relies on it, feel free to open an issue on GitHub or contact me
+and maybe we can work something out. Maybe a separate dedicated tool could work,
+or extended support for Knip v5.
+
+## Upgrade today
+
+```sh
+npm install -D knip@latest
+```
+
+## Deep closing thoughts...
+
+Remember, Knip it before you ship it! Have a great day ☀️
+
+[1]: ./slim-down-to-speed-up.md
+[2]: ./knip-v4.mdx
+[3]: https://oxc.rs/docs/guide/usage/parser
+[4]: https://github.com/overlookmotel
+[5]: https://github.com/Boshen
+[6]: https://oxc.rs
+[7]: https://try.venz.dev/?type=bar&labelX=Knip&labelY=duration+(s)&label=astro&label=query&label=rolldown&label=sentry&label=typescript&l=v5.88.0&l=v6.0.0&data=4*2&data=3.8*1.7&data=3.7*1.7&data=11*4&data=3.7*0.9
+[8]: https://cdn.venz.dev/i/chart.svg?pad=0&type=bar&labelX=Knip&labelY=duration+(s)&label=astro&label=query&label=rolldown&label=sentry&label=typescript&l=v5.88.0&l=v6.0.0&data=4*2&data=3.8*1.7&data=3.7*1.7&data=11*4&data=3.7*0.9&theme=dark
+[9]: https://github.com/withastro/astro
+[10]: https://github.com/TanStack/query
+[11]: https://github.com/rolldown/rolldown
+[12]: https://github.com/getsentry/sentry
+[13]: https://github.com/microsoft/TypeScript
+[14]: ../reference/configuration.md#tags
+[15]: ../features/reporters.md#custom-reporters
+[16]: ../features/reporters.md#json
+[17]: ../reference/integrations.md
+[18]: https://github.com/microsoft/typescript-go/discussions/455
+[19]: https://github.com/microsoft/typescript-go/tree/main/_packages/api
+[20]: https://github.com/search?q=classMembers%20path%3Aknip.json&type=code

package/src/docs/docs/blog/release-notes-v2.md

@@ -1,7 +1,7 @@
 ---
 title: Release Notes v2
 sidebar:
-  order: 9
+  order: 10
 ---
 
 _2023-03-22_

package/src/docs/docs/blog/slim-down-to-speed-up.md

@@ -2,7 +2,7 @@
 title: Slim down to speed up
 date: 2023-12-14
 sidebar:
-  order: 6
+  order: 7
 ---
 
 _Published: 2023-12-14_

package/src/docs/docs/blog/state-of-knip.md

@@ -2,7 +2,7 @@
 title: The State of Knip
 date: 2025-02-28
 sidebar:
-  order: 2
+  order: 3
 ---
 
 _Published: 2025-02-28_

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

@@ -2,7 +2,7 @@
 title: Two Years
 date: 2024-10-04
 sidebar:
-  order: 3
+  order: 4
 ---
 
 _Published: 2024-10-04_

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

@@ -71,7 +71,7 @@ ts-prune
 knip --include exports,types,nsExports,nsTypes
 ```
 
-Use `knip --exports` to also include class and enum members.
+Use `knip --exports` to also include enum and namespace members.
 
 **Project status**: The project is archived and recommends Knip.
 
@@ -87,7 +87,7 @@ ts-unused-exports
 knip --include exports,types,nsExports,nsTypes
 ```
 
-Use `knip --exports` to also include class and enum members.
+Use `knip --exports` to also include enum and namespace members.
 
 ### tsr
 

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

@@ -11,8 +11,7 @@ following [issue types][1]:
 
 - Remove `export` keyword for unused exports, re-exports, and exported types
 - Remove `export default` keywords for unused default exports
-- Remove unused enum members
-- Remove unused class members (disabled by default)
+- Remove unused enum and namespace members
 - Remove unused `dependencies` and `devDependencies` from `package.json`
 - Remove unused files
 - Remove unused catalog entries
@@ -288,37 +287,9 @@ Unused dependencies are removed from `package.json`:
  }
 ```
 
-### Class members   <Badge text="experimental" variant="caution" />
-
-Unused members of classes can be removed:
-
-```diff title="file.ts"
-export class Rectangle {
-  constructor(public width: number, public height: number) {}
-
--  static Key = 1;
-+
-
-  area() {
-    return this.width * this.height;
-  }
-
--  public get unusedGetter(): string {
--    return 'unusedGetter';
--  }
-}
-```
-
-Currently Knip might be too eager removing class members when they're not
-referenced internally but meant to be called by an external library. For
-instance, Knip might think `componentDidMount` and `render` in React class
-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`:
+Unused [catalog][4] entries are removed from `pnpm-workspace.yaml`:
 
 ```diff title="pnpm-workspace.yaml"
  packages:
@@ -344,5 +315,4 @@ Operations that auto-fix does not (yet) perform and why:
 [1]: ../reference/issue-types.md
 [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
+[4]: https://pnpm.io/catalogs

package/src/docs/docs/features/reporters.md

@@ -29,7 +29,6 @@ object per file structured like this:
 
 ```json
 {
-  "files": ["src/unused.ts"],
   "issues": [
     {
       "file": "package.json",
@@ -55,18 +54,22 @@ object per file structured like this:
         { "name": "unusedEnum", "line": 3, "col": 13, "pos": 71 },
         { "name": "unusedType", "line": 8, "col": 14, "pos": 145 }
       ],
-      "enumMembers": {
-        "MyEnum": [
-          { "name": "unusedMember", "line": 13, "col": 3, "pos": 167 },
-          { "name": "unusedKey", "line": 15, "col": 3, "pos": 205 }
-        ]
-      },
-      "classMembers": {
-        "MyClass": [
-          { "name": "unusedMember", "line": 40, "col": 3, "pos": 687 },
-          { "name": "unusedSetter", "line": 61, "col": 14, "pos": 1071 }
-        ]
-      },
+      "enumMembers": [
+        {
+          "namespace": "MyEnum",
+          "name": "unusedMember",
+          "line": 13,
+          "col": 3,
+          "pos": 167
+        },
+        {
+          "namespace": "MyEnum",
+          "name": "unusedKey",
+          "line": 15,
+          "col": 3,
+          "pos": 205
+        }
+      ],
       "duplicates": ["Registration", "default"]
     }
   ]

package/src/docs/docs/features/rules-and-filters.md

@@ -52,6 +52,7 @@ Knip has shortcuts to include only specific issue types.
    - `exports`
    - `types`
    - `enumMembers`
+   - `namespaceMembers`
    - `duplicates`
 
 3. The `--files` flag is a shortcut for `--include files`
@@ -73,7 +74,6 @@ Example:
 {
   "rules": {
     "files": "warn",
-    "classMembers": "off",
     "duplicates": "off"
   }
 }

package/src/docs/docs/guides/handling-issues.mdx

@@ -517,7 +517,7 @@ option][39] to tell Knip where to find the icon types:
 Where `[framework]` is the name of the framework you're using (see [available
 types][42]).
 
-**Solution**: try [--include-libs][43] or configure [paths][39].
+**Solution**: configure [paths][39].
 
 ## Unused exports
 
@@ -525,8 +525,8 @@ By default, Knip does not report unused exports of `entry` files.
 
 The most common causes for unused exports include:
 
-- [Namespace enumerations][44]
-- [External libraries][45]
+- [Namespace enumerations][43]
+- [External libraries][44]
 
 Use the `--exports` flag to [filter][17] and focus only on issues related to
 exports:
@@ -535,7 +535,7 @@ exports:
 knip --exports
 ```
 
-Use [includeEntryExports][46] to report unused exports of entry files as well.
+Use [includeEntryExports][45] to report unused exports of entry files as well.
 This can be set per workspace.
 
 ### Namespace enumerations
@@ -547,7 +547,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][47] to see all related patterns.
+See [namespace imports][46] to see all related patterns.
 
 ### External libraries
 
@@ -578,27 +578,16 @@ non-standard consumption of your exports? Here's an example:
 </Tabs>
 
 Knip understands `Apple` is used, since it's standard usage. But `Orange` is
-referenced through a function of an external library. For performance reasons,
-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:
-
-```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][48] are included (that
-feature comes with roughly the same performance penalty).
+referenced through a function of an external library. Knip includes external
+type definitions to trace such usage, but in some cases it may not be able to
+follow the reference through the library's API.
 
 ### Exclude exports from the report
 
 To exclude false positives from the report, there are a few options:
 
-- [Ignore exports used in file][49] for exports used internally.
-- Individual exports can be [tagged using JSDoc syntax][50].
+- [Ignore exports used in file][47] for exports used internally.
+- Individual exports can be [tagged using JSDoc syntax][48].
 - Have the export in an entry file:
 
   - Add the file to the `entry` file patterns array in the configuration.
@@ -609,50 +598,47 @@ 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][46]
+be exported from an entry file. In that case, use [--include-entry-exports][45]
 to make Knip also report unused exports in entry files.
 
 The exports of non-standard extensions like `.astro`, `.mdx`, `.vue` or
 `.svelte` are not available by default. See [compilers][21] for more details on
 how to include them.
 
-### Class members
+### Enum members
 
-Unused members of exported classes are not reported by default, here's how to
-enable them:
+Unused enums and unused members of exported enums are reported by default.
+Reporting such members can be disabled:
 
 ```sh
-knip --include classMembers
+knip --exclude enumMembers
 ```
 
-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][50].
+Individual enum members can be [tagged using JSDoc syntax][48].
 
-Classes exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][46] to make Knip also report members of unused exports
+Enums exported from entry files are ignored, and so are their members. Use
+[--include-entry-exports][45] to make Knip also report members of unused exports
 in entry files.
 
-### Enum members
+### Namespace members
 
-Unused enums and unused members of exported enums are reported by default.
+Unused members of exported TypeScript namespaces are reported by default.
 Reporting such members can be disabled:
 
 ```sh
-knip --exclude enumMembers
+knip --exclude namespaceMembers
 ```
 
-Individual enum members can be [tagged using JSDoc syntax][50].
+Individual namespace members can be [tagged using JSDoc syntax][48].
 
-Enums exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][46] to make Knip also report members of unused exports
+Namespaces exported from entry files are ignored, and so are their members. Use
+[--include-entry-exports][45] 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][51] and open an
+false positive), feel free to create a [minimal reproduction][49] and open an
 issue on GitHub. It'll make Knip better for everyone!
 
 [1]: #unused-files
@@ -697,12 +683,10 @@ issue on GitHub. It'll make Knip better for everyone!
 [40]: ../reference/configuration.md#ignoreunresolved
 [41]: https://www.npmjs.com/package/unplugin-icons
 [42]: https://github.com/unplugin/unplugin-icons/tree/main/types
-[43]: ../reference/cli.md#--include-libs
-[44]: #namespace-enumerations
-[45]: #external-libraries
-[46]: ../reference/configuration.md#includeentryexports
-[47]: ../guides/namespace-imports.md
-[48]: #class-members
-[49]: ../reference/configuration.md#ignoreexportsusedinfile
-[50]: ../reference/jsdoc-tsdoc-tags.md
-[51]: ../guides/issue-reproduction.md
+[43]: #namespace-enumerations
+[44]: #external-libraries
+[45]: ../reference/configuration.md#includeentryexports
+[46]: ../guides/namespace-imports.md
+[47]: ../reference/configuration.md#ignoreexportsusedinfile
+[48]: ../reference/jsdoc-tsdoc-tags.md
+[49]: ../guides/issue-reproduction.md

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

@@ -87,14 +87,10 @@ development][12].
 
 [1]: https://github.com/webpro-nl/knip/issues?q=is%3Aissue
 [2]: https://knip.dev/reference/known-issues
-[3]:
-  https://codesandbox.io/p/devbox/github/webpro-nl/knip/main/templates/issue-reproduction/basic
-[4]:
-  https://stackblitz.com/github/webpro-nl/knip/tree/main/templates/issue-reproduction/basic
-[5]:
-  https://codesandbox.io/p/devbox/github/webpro-nl/knip/main/templates/issue-reproduction/monorepo
-[6]:
-  https://stackblitz.com/github/webpro-nl/knip/tree/main/templates/issue-reproduction/monorepo
+[3]: https://codesandbox.io/p/devbox/github/webpro-nl/knip/main/templates/issue-reproduction/basic
+[4]: https://stackblitz.com/github/webpro-nl/knip/tree/main/templates/issue-reproduction/basic
+[5]: https://codesandbox.io/p/devbox/github/webpro-nl/knip/main/templates/issue-reproduction/monorepo
+[6]: 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/blob/main/.github/DEVELOPMENT.md#tests