@knip/mcp 0.0.2 → 0.0.3

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

@@ -1,26 +1,37 @@
 ---
 title: Knip for Editors & Agents
-date: 2025-12-18
+date: 2025-12-17
 sidebar:
   order: 1
 ---
 
-_Published: 2025-12-18_
+_Published: 2025-12-17_
+
+Three years in, Knip has founds 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.
+
+Don't forget... Knip it before you ship it!
 
 ## VS Code Extension
 
 This one is for you.
 
-[The usual suspects][1] like red squiggles for unused exports are there. What
+[The usual suspects][3] 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][2]:
+check. We're starting out with [3 key features][4]:
 
 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].
+
 ## MCP Server
 
 Configuring Knip has always been a major headache to many. No more. Tell your
@@ -28,7 +39,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][3] separately and built into the VS Code
+The [MCP Server is available][6] separately and built into the VS Code
 Extension.
 
 ## Language Server
@@ -40,25 +51,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][4]
+[language-server/README.md][7]
 
 ## Screenshots
 
-- [Lint Findings][1]
-- [Imports & Exports][2]
-- [Contention][5]
-  - [Circular Dependencies][6]
-  - [Conflicts][7]
-  - [Branching][8]
-- [VS Code Extension Settings][9]
+- [Lint Findings][3]
+- [Imports & Exports][4]
+- [Contention][8]
+  - [Circular Dependencies][9]
+  - [Conflicts][10]
+  - [Branching][11]
+- [VS Code Extension Settings][12]
 
 ### Lint Findings
 
-![Lint Findings][10]
+![Lint Findings][13]
 
 ### Imports & Exports
 
-![hover][11]
+![hover][14]
 
 ### Contention
 
@@ -70,7 +81,7 @@ branched/diamond-shaped import chains.
 
 If an import is part of a circular dependency, Knip will display:
 
-![Circular Dependencies][12]
+![Circular Dependencies][15]
 
 #### Conflicts
 
@@ -78,7 +89,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][13]
+![Conflicts][16]
 
 #### Branching
 
@@ -86,24 +97,28 @@ 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][14]
+![Branching][17]
 
 ### VS Code Extension Settings
 
-![VS Code Extension Settings][15]
-
-[1]: #lint-findings
-[2]: #imports--exports
-[3]: https://github.com/webpro-nl/knip/blob/main/packages/mcp-server/README.md
-[4]: https://www.npmjs.com/package/@knip/mcp
-[5]: #contention
-[6]: #circular-dependencies
-[7]: #conflicts
-[8]: #branching
-[9]: #vs-code-extension-settings
-[10]: /screenshots/editors-and-agents/diagnostics.webp
-[11]: /screenshots/editors-and-agents/imports-exports.webp
-[12]: /screenshots/editors-and-agents/circular-dependency.webp
-[13]: /screenshots/editors-and-agents/conflict.webp
-[14]: /screenshots/editors-and-agents/branch.webp
-[15]: /screenshots/editors-and-agents/vscode-extension-settings.webp
+![VS Code Extension Settings][18]
+
+[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://www.npmjs.com/package/@knip/mcp
+[7]:
+  https://github.com/webpro-nl/knip/blob/main/packages/language-server/README.md
+[8]: #contention
+[9]: #circular-dependencies
+[10]: #conflicts
+[11]: #branching
+[12]: #vs-code-extension-settings
+[13]: /screenshots/editors-and-agents/diagnostics.webp
+[14]: /screenshots/editors-and-agents/imports-exports.webp
+[15]: /screenshots/editors-and-agents/circular-dependency.webp
+[16]: /screenshots/editors-and-agents/conflict.webp
+[17]: /screenshots/editors-and-agents/branch.webp
+[18]: /screenshots/editors-and-agents/vscode-extension-settings.webp

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

@@ -0,0 +1,30 @@
+---
+title: A Brief History Of Knip
+date: 2023-10-15
+sidebar:
+  order: 7
+---
+
+_Published: 2023-10-15_
+
+If you are fond of short lists and brief histories, then this page was written
+just for you!
+
+- 2022-10-04: The [initial commit][1]. Still so tiny at that point, but the seed
+  was planted. Starting out with finding unused files and exports, the name was
+  Exportman! 🦸
+- 2022-10-09: Big plans and a rename 5 days later, the first published version
+  of Knip was [v0.1.2][2].
+- 2022-11-22: Unused dependencies and support for workspaces and plugins in the
+  [first alpha of v1][3].
+- 2023-01-10: Lots of testing and fixes led to [Knip v1][4].
+- 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
+[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
+[5]: https://github.com/webpro-nl/knip/issues/73
+[6]: ./knip-v3.mdx

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

@@ -0,0 +1,124 @@
+---
+title: Knip for Editors & Agents
+date: 2025-12-17
+sidebar:
+  order: 1
+---
+
+_Published: 2025-12-17_
+
+Three years in, Knip has founds 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.
+
+Don't forget... Knip it before you ship it!
+
+## VS Code Extension
+
+This one is for you.
+
+[The usual suspects][3] 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]:
+
+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].
+
+## MCP Server
+
+Configuring Knip has always been a major headache to many. No more. Tell your
+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][6] separately and built into the VS Code
+Extension.
+
+## Language Server
+
+The VS Code Extension and the MCP Server are powered by the new Language Server.
+It's a custom server that builds the full module graph of your project, and
+provides a session with a graph explorer to request all sorts of interesting
+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][7]
+
+## Screenshots
+
+- [Lint Findings][3]
+- [Imports & Exports][4]
+- [Contention][8]
+  - [Circular Dependencies][9]
+  - [Conflicts][10]
+  - [Branching][11]
+- [VS Code Extension Settings][12]
+
+### Lint Findings
+
+![Lint Findings][13]
+
+### Imports & Exports
+
+![hover][14]
+
+### Contention
+
+The IDE extension shows extra issues in the tree views like circular
+dependencies. We're starting out with some extra novelties like conflicting and
+branched/diamond-shaped import chains.
+
+#### Circular Dependencies
+
+If an import is part of a circular dependency, Knip will display:
+
+![Circular Dependencies][15]
+
+#### Conflicts
+
+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][16]
+
+#### Branching
+
+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][17]
+
+### VS Code Extension Settings
+
+![VS Code Extension Settings][18]
+
+[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://www.npmjs.com/package/@knip/mcp
+[7]:
+  https://github.com/webpro-nl/knip/blob/main/packages/language-server/README.md
+[8]: #contention
+[9]: #circular-dependencies
+[10]: #conflicts
+[11]: #branching
+[12]: #vs-code-extension-settings
+[13]: /screenshots/editors-and-agents/diagnostics.webp
+[14]: /screenshots/editors-and-agents/imports-exports.webp
+[15]: /screenshots/editors-and-agents/circular-dependency.webp
+[16]: /screenshots/editors-and-agents/conflict.webp
+[17]: /screenshots/editors-and-agents/branch.webp
+[18]: /screenshots/editors-and-agents/vscode-extension-settings.webp

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

@@ -0,0 +1,88 @@
+---
+title: Announcing Knip v3
+date: 2023-10-15
+sidebar:
+  order: 8
+---
+
+import { Tabs, TabItem } from '@astrojs/starlight/components';
+
+_Published: 2023-10-15_
+
+Lots of new users got introduced to Knip, coming with clear bug reports, helpful
+insights, superb reproductions and great suggestions this year. You're all a
+friendly and helpful bunch! Recently I've opened a Discord channel where more
+communication, collaboration, ideas and updates are happening: feel free to join
+[The Knip Barn][1]!
+
+Today, Knip has [over 140k weekly downloads on npm][2], [almost 4000 stars on
+GitHub][3], and [over 500 repositories][4] using it. While numbers are just
+numbers, they do add to the positive feedback I'm receiving daily. Everything
+combined makes me think I'm on the right track which is very motivating to keep
+working on Knip.
+
+## So... What's Been Cooking Lately?
+
+- Migration to a monorepo setup
+- This very website built with Starlight 🌟
+- Extended documentation for just about everything
+- Improved JSON reporter for external integrations (e.g. [GitHub Action][5])
+- Some breaking changes, but you probably don't need to make any changes
+
+## Breaking Changes
+
+A major bump comes with breaking changes, but most likely no changes necessary
+on your end:
+
+- Removed support for Node.js v16, Knip v3 requires at least Node.js v18.6
+- Simplified [exit codes][6]
+- [Production mode][7] now includes types by default (add `--exclude types` for
+  previous behavior)
+- Removed `--ignore-internal` flag; [`@internal`][8] exports ignored in
+  production mode now
+- The `--debug-file-filter` flag is removed
+- The `jsonExt` reporter is now the default [JSON reporter][9] (the previous one
+  is gone)
+- Moved `typescript` to `peerDependencies` (requires `>=5.0.4`)
+
+## Installation
+
+Try out the latest Knip v3 release today!
+
+<Tabs syncKey="pm">
+  <TabItem label="npm">
+    ```shell
+    npm install -D knip
+    ```
+  </TabItem>
+
+  <TabItem label="pnpm">
+    ```shell
+    pnpm add -D knip
+    ```
+  </TabItem>
+
+  <TabItem label="bun">
+    ```shell
+    bun add -D knip
+    ```
+  </TabItem>
+
+  <TabItem label="yarn">
+    ```shell
+    yarn add -D knip
+    ```
+  </TabItem>
+</Tabs>
+
+Remember, Knip it before you ship it! Have a great day ☀️
+
+[1]: https://discord.gg/r5uXTtbTpc
+[2]: https://www.npmjs.com/package/knip
+[3]: https://github.com/webpro-nl/knip/stargazers
+[4]: https://github.com/webpro-nl/knip/network/dependents
+[5]: https://github.com/marketplace/actions/knip-reporter
+[6]: ../reference/cli.md#exit-code
+[7]: ../features/production-mode.md
+[8]: ../reference/jsdoc-tsdoc-tags.md#internal
+[9]: ../features/reporters.md#json

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

@@ -0,0 +1,149 @@
+---
+title: Announcing Knip v4
+date: 2024-01-16
+sidebar:
+  order: 5
+---
+
+import { Tabs, TabItem } from '@astrojs/starlight/components';
+
+_Published: 2024-01-16_
+
+I'm happy to announce that Knip v4 is available!
+
+The work took over a month and the process of [slimming down to speed up][1]
+ended up really well: significant faster runs and reduced memory usage. In the
+meantime, v3 continued to receive more contributions, plugins and bug fixes.
+
+## Highlights
+
+Compared to v3, here are the highlights:
+
+- Performance: significant speed bump (up to 80%!)
+- Performance: globbing in combo with `.gitignore` is a lot more efficient
+- Configuration: [built-in compilers][2] (for Astro, MDX, Svelte & Vue)
+- The `ignore` option has been improved
+- Internal refactoring to serialize data for future improvements like caching.
+
+The actual performance win in your projects depends on various factors like size
+and complexity.
+
+## Major Changes
+
+The changes have been tested against various repositories, but it's possible
+that you will encounter false positives caused by the major refactoring that has
+been done. If you do, [please report][3]!
+
+### Unused Class Members
+
+Finding unused class members is no longer enabled by default. Here's why it's
+now opt-in:
+
+- When using Knip for the first time on a large repository it can crash after a
+  while with an out of memory error. This is a terrible experience.
+- Plenty of codebases don't use classes at all, keeping TS programs in memory is
+  a waste of resources.
+- Many configurations already exclude `classMembers` from the output.
+
+Enable unused class members by using the CLI argument or the configuration
+option:
+
+```shell
+knip --include classMembers
+```
+
+```json
+{
+  "include": ["classMembers"]
+}
+```
+
+Now that unused class members is opt-in and better organized within Knip, it
+might be interesting to start looking at opt-ins for other unused members, such
+as those of types and interfaces.
+
+By the way, enum members are "cheap" with the v4 refactor, so those are still
+included by default.
+
+### Compilers
+
+You can remove the `compilers` option from your configuration. Since you can
+override them, your custom compilers can stay where they are. This also means
+that you can go back from `knip.ts` to `knip.json` if you prefer.
+
+### Ignore Files
+
+The `ignore` option accepted patterns like `examples/`, but if you want to
+ignore the files inside this folder you should update to globs like
+`examples/**`.
+
+## What's Next?
+
+The refactoring for this release opens the door to more optimizations, such as
+caching. I'm also very excited to see how deeper integrations such as in GitHub
+Actions or IDEs like VS Code or WebStorm may further develop.
+
+Remember, if you are you using Knip at work your company can [sponsor me][4]!
+
+## One More Thing...
+
+An idea I've been toying with is "tagged exports". The idea is that you can tag
+exports in a JSDoc comment. The tag does not need to be part of the JSDoc or
+TSDoc spec. For example:
+
+```ts
+/** @custom */
+export const myExport = 1;
+```
+
+Then, include or exclude such tagged exports from the report like so:
+
+```shell
+knip --experimental-tags=+custom
+knip --experimental-tags=-custom,-internal
+```
+
+This way, you can either focus on or ignore specific tagged exports with tags
+you define yourself. This also works for individual class or enum members.
+
+Once this feature is intuitive and stable, the `experimental` flag will be
+removed and option(s) added to the Knip configuration file. The docs are in the
+[CLI reference][5].
+
+## Let's Go!
+
+What are you waiting for? Start using Knip v4 today!
+
+<Tabs syncKey="pm">
+  <TabItem label="npm">
+    ```shell
+    npm install -D knip
+    ```
+  </TabItem>
+
+  <TabItem label="pnpm">
+    ```shell
+    pnpm add -D knip
+    ```
+  </TabItem>
+
+  <TabItem label="bun">
+    ```shell
+    bun add -D knip
+    ```
+  </TabItem>
+
+  <TabItem label="yarn">
+    ```shell
+    yarn add -D knip
+    ```
+  </TabItem>
+</Tabs>
+
+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
+[4]: https://github.com/sponsors/webpro
+[5]: ../reference/cli#--experimental-tags