@knip/mcp 0.0.13 → 0.0.15

package/package.json

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

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

@@ -108,7 +108,7 @@ configured.
 
 :::tip[Plugins result in less configuration]
 
-Plugins uses entry file patterns as defined in the configuration files of these
+Plugins uses entry file patterns as defined in your configuration file of these
 tools. So you don't need to repeat this in your Knip configuration.
 
 :::
@@ -242,7 +242,8 @@ dependency.
 
 :::tip[Summary]
 
-Plugins can find additional entry files when parsing config files.
+In your config files, plugins can find additional entry files and also other
+config files recursively.
 
 :::
 
@@ -285,7 +286,9 @@ 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.
+When plugins dynamically load configuration files, conditional dependencies may
+not be detected if the condition evaluates differently during analysis. See
+[conditional or dynamic dependencies][9] for details and workarounds.
 
 :::
 
@@ -299,7 +302,7 @@ node --loader tsx scripts/deploy.ts
 playwright test -c playwright.web.config.ts
 ```
 
-Please see [script parser][9] for more details.
+Please see [script parser][10] for more details.
 
 ## Summary
 
@@ -315,12 +318,12 @@ Plugins are configured with two distinct types of files:
 :::
 
 [1]: ../reference/plugins.md
-[2]: ../guides/writing-a-plugin.md
+[2]: ../writing-a-plugin/index.md
 [3]: #configuration-files
 [4]: #entry-files
 [5]: #command-line-arguments
 [6]: ./entry-files.md
 [7]: ../reference/plugins/eslint.md
 [8]: ../reference/plugins/vitest.md
-[9]: ../features/script-parser.md
-[10]: ../guides/handling-issues.mdx#conditional-or-dynamic-dependencies
+[9]: ../guides/handling-issues.mdx#conditional-or-dynamic-dependencies
+[10]: ../features/script-parser.md

package/src/docs/docs/guides/configuring-project-files.md

@@ -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 exclude files
-from analysis.
+Use `ignore*` to suppress specific issues in matching files; it does not exclude
+files from analysis.
 
 :::
 
@@ -200,6 +200,6 @@ automatically added as well.
 
 [1]: ../typescript/unused-exports.md
 [2]: ../explanations/entry-files.md
-[3]: ../reference/configuration#ignoreexportsusedinfile
+[3]: ../reference/configuration.md#ignoreexportsusedinfile
 [4]: ../features/production-mode.md
 [5]: ../explanations/plugins.md#entry-files

package/src/docs/docs/guides/contributing.md

@@ -20,5 +20,5 @@ contributes to that goal is welcome!
 [1]: https://github.com/webpro-nl/knip
 [2]: ./issue-reproduction.md
 [3]: https://github.com/webpro-nl/knip/blob/main/.github/CONTRIBUTING.md
-[4]: ./writing-a-plugin.md
+[4]: ../writing-a-plugin/index.md
 [5]: https://github.com/webpro-nl/knip/blob/main/.github/DEVELOPMENT.md

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

@@ -294,7 +294,7 @@ Some packages have the same name as a Node.js builtin (for instance `buffer` or
 **Solution**: if Knip reports such a dependency as unused, add it to
 [ignoreDependencies][22].
 
-#### Conditional or dynamic dependencies
+### 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
@@ -319,11 +319,11 @@ 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.
+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"
 {
@@ -420,9 +420,9 @@ example:
 ```
 
 This example works fine without anything reported, as the `@commitlint/cli`
-package includes the `commitlint` binary. However, some script may contain
-`npx commitlint` and here Knip assumes `commitlint` is the name of the package.
-This technically works, as `commitlint` is a transitive dependency of
+package includes the `commitlint` binary. However, some script may contain `npx
+commitlint` and here Knip assumes `commitlint` is the name of the package. This
+technically works, as `commitlint` is a transitive dependency of
 `@commitlint/cli`.
 
 **Solution**: use `npx @commitlint/cli`
@@ -473,8 +473,8 @@ The first import is resolved properly, because `.vue` is a known extension if
 the Vue plugin is enabled. The second import might not be resolved, because
 `.svg` is not a known extension.
 
-The recommendation is to always add the extension when importing such files,
-similar to how standard ES Modules specifies file extensions are necessary.
+**Solution**: include the extension. Hosts supporting ES Modules (e.g. Node.js,
+browsers) require a file extension for import specifiers.
 
 ### Unrecognized path aliases
 
@@ -488,9 +488,9 @@ but not those in e.g. Webpack or Vite configurations.
 
 External libraries may use aliased imports that aren't resolved by Knip.
 
-For instance, [unplugin-icons][10] does this to import icons from icon sets as
+For instance, [unplugin-icons][39] does this to import icons from icon sets as
 components. Such imports are reported as unused. Use the [`paths` configuration
-option][13] to tell Knip where to find the icon types:
+option][37] to tell Knip where to find the icon types:
 
 ```json title="knip.json"
 {
@@ -501,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][39]).
+types][40]).
 
-**Solution**: try [--include-libs][40] or configure [paths][37].
+**Solution**: try [--include-libs][41] or configure [paths][37].
 
 ## Unused exports
 
@@ -511,8 +511,8 @@ By default, Knip does not report unused exports of `entry` files.
 
 The most common causes for unused exports include:
 
-- [Namespace enumerations][41]
-- [External libraries][40]
+- [Namespace enumerations][42]
+- [External libraries][43]
 
 Use the `--exports` flag to [filter][15] and focus only on issues related to
 exports:
@@ -521,7 +521,7 @@ exports:
 knip --exports
 ```
 
-Use [includeEntryExports][42] to report unused exports of entry files as well.
+Use [includeEntryExports][44] to report unused exports of entry files as well.
 This can be set per workspace.
 
 ### Namespace enumerations
@@ -533,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][43] to see all related patterns.
+See [namespace imports][45] to see all related patterns.
 
 ### External libraries
 
@@ -553,7 +553,6 @@ non-standard consumption of your exports? Here's an example:
       resolveComponent: components => components.Orange,
     });
     ```
-
   </TabItem>
 
   <TabItem label="components.js">
@@ -570,23 +569,24 @@ 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][44] flag:
+[--include-libs][41] 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][45] are included (that
+if you need it. This flag is implied when [classMembers][46] 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][46] for exports used internally.
-- Individual exports can be [tagged using JSDoc syntax][47].
+- [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.
   - Move the export(s) to an entry file.
   - Add the file to the `exports` field of `package.json`
@@ -595,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][42]
+be exported from an entry file. In that case, use [--include-entry-exports][44]
 to make Knip also report unused exports in entry files.
 
 The exports of non-standard extensions like `.astro`, `.mdx`, `.vue` or
@@ -614,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][47].
+Individual class members can be [tagged using JSDoc syntax][48].
 
 Classes exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][42] to make Knip also report members of unused exports
+[--include-entry-exports][44] to make Knip also report members of unused exports
 in entry files.
 
 ### Enum members
@@ -629,16 +629,16 @@ Reporting such members can be disabled:
 knip --exclude enumMembers
 ```
 
-Individual enum members can be [tagged using JSDoc syntax][47].
+Individual enum members can be [tagged using JSDoc syntax][48].
 
 Enums exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][42] to make Knip also report members of unused exports
+[--include-entry-exports][44] 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][48] 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
@@ -660,34 +660,33 @@ issue on GitHub. It'll make Knip better for everyone!
 [17]: ../features/source-mapping.md
 [18]: ../features/script-parser.md
 [19]: ../features/compilers.md
-[20]: ./writing-a-plugin.md
+[20]: ../writing-a-plugin/index.md
 [21]: ../reference/plugins.md
 [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]: #dependencies-named-after-nodejs-builtins
 [31]: #unlisted-binaries
-[32]:
-  https://github.com/webpro-nl/knip/blob/b70958a58ea255ee7a7831e404786da807ca93d7/packages/knip/src/constants.ts#L37-L139
+[32]: https://github.com/webpro-nl/knip/blob/e031018e676c47d84873cc2403251c0111ef318d/packages/knip/src/constants.ts#L39-L148
 [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
+[39]: https://www.npmjs.com/package/unplugin-icons
+[40]: https://github.com/unplugin/unplugin-icons/tree/main/types
+[41]: ../reference/cli.md#--include-libs
+[42]: #namespace-enumerations
+[43]: #external-libraries
+[44]: ../reference/configuration.md#includeentryexports
+[45]: ../guides/namespace-imports.md
+[46]: #class-members
+[47]: ../reference/configuration.md#ignoreexportsusedinfile
+[48]: ../reference/jsdoc-tsdoc-tags.md
+[49]: ../guides/issue-reproduction.md

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

@@ -42,6 +42,10 @@ Before opening an issue, please make sure you:
 Please file only a single issue at a time, so each of them can be labeled and
 tracked separately.
 
+There is no need to open an issue if you're going to submit a pull request to
+close it right away anyway. In that case it's preferred to keep things central
+in either an issue or pull request.
+
 ## Templates
 
 A convenient way to create a minimal reproduction is by starting with one of

package/src/docs/docs/guides/troubleshooting.md

@@ -121,7 +121,7 @@ to [open an issue on GitHub][14].
 [2]: #exceptions-thrown-by-knip
 [3]: #debug
 [4]: #trace
-[5]: ../guides/handling-issues.md
+[5]: ../guides/handling-issues.mdx
 [6]: ./issue-reproduction.md
 [7]: ../reference/known-issues.md
 [8]: ../reference/cli.md#--workspace-dir

package/src/docs/docs/index.mdx

@@ -31,7 +31,7 @@ import Contributors from '../../components/Contributors.astro';
 
 :::section{.badges}
 
-[![NPM Version][2]][1] [![NPM Downloads][3]][1] [![GitHub Repo   stars][5]][4]
+[![NPM Version][2]][1] [![NPM Downloads][3]][1] [![GitHub Repo stars][5]][4]
 
 :::
 
@@ -138,10 +138,10 @@ A curated selection of articles about Knip, most recent first:
 [3]: https://img.shields.io/npm/dm/knip?color=f56e0f
 [4]: https://github.com/webpro-nl/knip
 [5]: https://img.shields.io/github/stars/webpro-nl/knip?style=flat&color=f56e0f
-[6]: ./sponsors
+[6]: /sponsors
 [7]: https://webpro.nl/hire-me
 [8]: ./reference/plugins.md
-[9]: ./playground
+[9]: /playground
 [10]: ./guides/troubleshooting.md
 [11]: https://www.jamesshopland.com
 [12]: https://blog.val.town/gardening-dependencies

package/src/docs/docs/overview/features.md

@@ -44,7 +44,7 @@ Also see [related tooling][2].
 [4]: ../reference/cli.md#--cache
 [5]: ../guides/working-with-commonjs.md
 [6]: ../features/compilers.md
-[7]: ../guides/troubleshooting.md#issues-reported-by-knip
+[7]: ../guides/troubleshooting.md#debug
 [8]: ../features/rules-and-filters.md#filters
 [9]: ../features/auto-fix.mdx#format
 [10]: ../reference/jsdoc-tsdoc-tags.md
@@ -63,4 +63,4 @@ Also see [related tooling][2].
 [23]: ../features/production-mode.md#strict-mode
 [24]: ../guides/troubleshooting.md#trace
 [25]: ../reference/cli.md#--watch
-[26]: ../features/monorepos-and-workspaces#lint-a-single-workspace
+[26]: ../features/monorepos-and-workspaces.md#lint-a-single-workspace

package/src/docs/docs/overview/getting-started.mdx

@@ -77,7 +77,17 @@ If the output makes sense to you, feel free to go to the next page:
 
 ## Too Much?
 
-In large or complex codebases the output might be overwhelming. Start by
+In large or complex codebases the output might be overwhelming.
+
+:::tip[NEW]
+
+Use the new [Knip Editor Extension][3] and let your coding agent configure Knip
+for you. The built-in MCP Server will intelligently craft a custom `knip.json`
+based on the documentation and configuration hints.
+
+:::
+
+Start by
 limiting the number of shown issues per type:
 
 <Tabs syncKey="pm">
@@ -108,12 +118,12 @@ limiting the number of shown issues per type:
 
 The output is easier to digest and may include some configuration hints to get
 an idea of what's left to configure. Many unused files? Go to [configuration][2]
-and follow up with [troubleshooting][3] if needed.
+and follow up with [troubleshooting][4] if needed.
 
 :::tip
 
 Do not use the `ignore` option just to get rid of unwanted output. Read
-[Configuring Project Files][4] to get the most out of Knip.
+[Configuring Project Files][5] to get the most out of Knip.
 
 :::
 
@@ -191,5 +201,6 @@ already.
 
 [1]: /playground
 [2]: ./configuration.md
-[3]: ../guides/troubleshooting.md
-[4]: ../guides/configuring-project-files.md
+[3]: ../blog/for-editors-and-agents.md
+[4]: ../guides/troubleshooting.md
+[5]: ../guides/configuring-project-files.md

package/src/docs/docs/reference/configuration.md

@@ -180,6 +180,13 @@ notation below is valid and will report only exports tagged `@lintignore` or
 }
 ```
 
+:::caution
+
+Tags must not contain hyphens or plus symbols, so it is recommended to stick to
+letters and avoid snake-case.
+
+:::
+
 Also see [JSDoc & TSDoc Tags][8].
 
 ### `treatConfigHintsAsErrors`

package/src/docs/docs/reference/faq.md

@@ -408,7 +408,6 @@ Examples of features that have been requested include:
   - Unused object members (and e.g. React component props)
   - Unused object props in function return values
 - Analyze workspaces in parallel
-- Plugins for editors like VS Code and WebStorm (LSP-based?)
 - Support Deno
 - Improve internal code structures and accessibility to support contributions
 - One-shot dead code removal (more comprehensive removal of unused variables,
@@ -427,7 +426,7 @@ require more development efforts and maintenance. Time is limited and
 [5]: ../explanations/why-use-knip.md#comprehensive
 [6]: #module-resolution
 [7]: ../features/script-parser.md
-[8]: ../guides/handling-issues.mdx#types-packages
+[8]: ../guides/handling-issues.mdx#type-definition-packages
 [9]: https://oxc.rs/docs/guide/usage/resolver.html
 [10]: ../guides/performance.md#workspace-sharing
 [11]: #whats-the-difference-between-workspaces-projects-and-programs