Remove links to closed "request plugin" issue

Author: webpro

packages/docs/src/content/docs/explanations/plugins.md

@@ -8,7 +8,7 @@ This page describes why Knip uses plugins and the difference between `config`
 and `entry` files.
 
 Knip has an extensive and growing [list of built-in plugins][1]. Feel free to
-[request a plugin][2] or even [write a plugin][3] so others can benefit too!
+[write a plugin][2] so others can benefit too!
 
 ## What does a plugin do?
 
@@ -17,13 +17,13 @@ in `package.json`. For instance, if `astro` is listed in `dependencies` or
 `devDependencies`, then the Astro plugin is enabled. And this means that this
 plugin will:
 
-- Handle [configuration files][4] like `astro.config.mjs`
-- Add [entry files][5] such as `src/pages/**/*.astro`
-- Define [command-line arguments][6]
+- Handle [configuration files][3] like `astro.config.mjs`
+- Add [entry files][4] such as `src/pages/**/*.astro`
+- Define [command-line arguments][5]
 
 ## Configuration files
 
-Knip uses [entry files][7] as starting points to scan your source code and
+Knip uses [entry files][6] as starting points to scan your source code and
 resolve other internal files and external dependencies. The dependency graph can
 be statically resolved through the `require` and `import` statements in those
 source files. However, configuration files reference external dependencies in
@@ -32,7 +32,7 @@ find those dependencies.
 
 ### Example: ESLint
 
-In the first example we look at [the ESLint plugin][8]. The default `config`
+In the first example we look at [the ESLint plugin][7]. The default `config`
 file patterns include `.eslintrc.json`. Here's a minimal example:
 
 ```json title=".eslintrc.json"
@@ -57,7 +57,7 @@ as unlisted. And vice versa, if there are any ESLint plugins listed in
 
 ### Example: Vitest
 
-The second example uses [the Vitest plugin][8]. Here's a minimal example of a
+The second example uses [the Vitest plugin][7]. Here's a minimal example of a
 Vitest configuration file:
 
 ```ts title="vitest.config.ts"
@@ -211,7 +211,7 @@ added as entry files by the GitHub Actions plugin.
 Additionally, the file `e2e/playwright.web.config.ts` is detected and will be
 handed over as a Playwright configuration file.
 
-Read more about this in [command-line arguments][6].
+Read more about this in [command-line arguments][5].
 
 ### webpack
 
@@ -293,7 +293,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][8] for more details.
 
 ## Summary
 
@@ -309,11 +309,10 @@ Plugins are configured with two distinct types of files:
 :::
 
 [1]: ../reference/plugins.md
-[2]: https://github.com/webpro-nl/knip/issues/483
-[3]: ../guides/writing-a-plugin.md
-[4]: #configuration-files
-[5]: #entry-files
-[6]: #command-line-arguments
-[7]: ./entry-files.md
-[8]: ../reference/plugins/eslint.md
-[9]: ../features/script-parser.md
+[2]: ../guides/writing-a-plugin.md
+[3]: #configuration-files
+[4]: #entry-files
+[5]: #command-line-arguments
+[6]: ./entry-files.md
+[7]: ../reference/plugins/eslint.md
+[8]: ../features/script-parser.md

packages/docs/src/content/docs/guides/handling-issues.mdx

@@ -119,15 +119,15 @@ example,
   reported as unused.
 
 Solution: [create a new plugin][13] for the tool or framework that's not [in the
-list][14] yet, or [request it][15]. Or work around it and add `entry` patterns
-and maybe ignore a dependency or two.
+list][14] yet. Or work around it and add `entry` patterns and maybe ignore a
+dependency or two.
 
 ### Incomplete plugin
 
 Files may be reported as unused if existing plugins do not include that entry
-file pattern yet. See the [plugins section of entry files][16] for more details.
+file pattern yet. See the [plugins section of entry files][15] for more details.
 
-Solution: [override plugin configuration][17] to customize default patterns for
+Solution: [override plugin configuration][16] to customize default patterns for
 existing plugins. Or even better: send a pull request to improve the plugin.
 
 ### Integrated monorepos
@@ -136,7 +136,7 @@ Multiple instances of configuration files like `.eslintrc` and
 `jest.config.json` across the repository may be reported as unused when working
 in a (mono)repo with a single `package.json`.
 
-Solution: see [integrated monorepos][18] for more details and how to configure
+Solution: see [integrated monorepos][17] for more details and how to configure
 plugins to target those configuration files.
 
 ### Build artifacts and ignored files
@@ -174,13 +174,13 @@ negated `project` patterns:
 
 First off: dependencies imported in unused files are reported as unused
 dependencies. That's why it's strongly recommended to try and remedy [unused
-files][19] first. Better `entry` and `project` file coverage will solve many
+files][18] first. Better `entry` and `project` file coverage will solve many
 cases of reported unused dependencies.
 
 The most common causes for unused and unlisted dependencies include:
 
-- [Missing or incomplete plugin][20]
-- [Unreachable code][21]
+- [Missing or incomplete plugin][19]
+- [Unreachable code][20]
 
 :::caution[Monorepo]
 
@@ -221,7 +221,7 @@ plugin could solve it, a last resort is to ignore it:
 ```
 
 If a binary (or "executable") is referenced you'll want to use `ignoreBinaries`
-instead. See [unlisted binaries][22].
+instead. See [unlisted binaries][21].
 
 ### Types packages
 
@@ -246,7 +246,7 @@ workspaces in a monorepo. This is an issue since we can't "assign" dependencies
 to other workspaces and incorrectly end up having "unlisted dependencies".
 
 Most notably, tools like TypeScript, Jest and legacy ESLint suffer from this.
-The new [ESLint flat config system][23] does not have this issue, so it's
+The new [ESLint flat config system][22] does not have this issue, so it's
 recommended to migrate if you haven't already.
 
 ## Unlisted dependencies
@@ -276,7 +276,7 @@ installed that includes that binary. It looks up the `bin` field in the
 reported as an unlisted binary as there is no package listed that contains it.
 
 Except for binaries that are most likely meant to be installed on the OS already
-and not installed from npm (details: [list in source][24]).
+and not installed from npm (details: [list in source][23]).
 
 ### Missing binaries
 
@@ -287,7 +287,7 @@ dependencies and binaries, or by not running Knip from the root of the
 repository.
 
 Solution: run Knip from the project root. From there you can [lint individual
-workspaces][25].
+workspaces][24].
 
 ### Example
 
@@ -329,8 +329,8 @@ By default, Knip does not report unused exports of `entry` files.
 
 The most common causes for unused exports include:
 
-- [Enumerations][26]
-- [External libraries][27]
+- [Enumerations][25]
+- [External libraries][26]
 
 Use the `--exports` flag to [filter][10] and focus on issues related to exports:
 
@@ -372,7 +372,7 @@ implicitly referenced in an enumeration like the following example:
   </TabItem>
 </Tabs>
 
-See [namepace imports][28] to see what patterns Knip does consider to be used
+See [namepace imports][27] to see what patterns Knip does consider to be used
 exports.
 
 ### External libraries
@@ -413,22 +413,22 @@ Knip does not include external type definitions by default so it won't see the
 export being referenced.
 
 To include the type definitions of external libraries, use the
-[--include-libs][29] flag:
+[--include-libs][28] 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][30] are included (that
+if you need it. This flag is implied when [classMembers][29] are included (that
 feature comes with roughly the same performance penalty).
 
 ### Exclude exports from the report
 
 To exclude unused exports from the report, there are a few options:
 
-- [Ignore exports used in file][31] for exports used internally.
-- Individual exports can be [tagged using JSDoc syntax][32].
+- [Ignore exports used in file][30] for exports used internally.
+- Individual exports can be [tagged using JSDoc syntax][31].
 - 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.
@@ -438,7 +438,7 @@ To exclude unused exports from the report, there are a few options:
 ## Missing 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][33]
+be exported from an entry file. In that case, use [--include-entry-exports][32]
 to make Knip also report unused exports in entry files.
 
 The exports of non-standard extensions like `.astro`, `.mdx`, `.vue` or
@@ -456,10 +456,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][32].
+Individual class members can be [tagged using JSDoc syntax][31].
 
 Classes exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][33] to make Knip also report members of unused exports
+[--include-entry-exports][32] to make Knip also report members of unused exports
 in entry files.
 
 ## Enum members
@@ -471,18 +471,18 @@ members can also be disabled altogether, for example:
 knip --exclude enumMembers
 ```
 
-Individual enum members can be [tagged using JSDoc syntax][32].
+Individual enum members can be [tagged using JSDoc syntax][31].
 
 Enums exported from entry files are ignored, and so are their members. Use
-[--include-entry-exports][33] to make Knip also report members of unused exports
+[--include-entry-exports][32] 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][34] and open an
+false positive), feel free to create a [minimal reproduction][33] and open an
 issue on GitHub. It'll make Knip better for everyone! Join the [Discord
-channel][35] to discuss any feedback or questions you may have.
+channel][34] to discuss any feedback or questions you may have.
 
 [1]: #dynamic-import-specifiers
 [2]: #unsupported-arguments-in-scripts
@@ -498,25 +498,24 @@ channel][35] to discuss any feedback or questions you may have.
 [12]: ../features/compilers.md
 [13]: ./writing-a-plugin.md
 [14]: ../reference/plugins.md
-[15]: https://github.com/webpro-nl/knip/issues/483
-[16]: ../explanations/plugins.md#entry-files
-[17]: ../explanations/entry-files.md#plugins
-[18]: ../features/integrated-monorepos.md
-[19]: #unused-files
-[20]: #missing-or-incomplete-plugin
-[21]: #unreachable-code
-[22]: #unlisted-binaries
-[23]: https://eslint.org/docs/latest/use/configure/configuration
-[24]:
+[15]: ../explanations/plugins.md#entry-files
+[16]: ../explanations/entry-files.md#plugins
+[17]: ../features/integrated-monorepos.md
+[18]: #unused-files
+[19]: #missing-or-incomplete-plugin
+[20]: #unreachable-code
+[21]: #unlisted-binaries
+[22]: https://eslint.org/docs/latest/use/configure/configuration
+[23]:
   https://github.com/webpro-nl/knip/blob/6f561ff09b4f1bf36585b64210ee34ea27ae04ea/packages/knip/src/constants.ts#L32-L133
-[25]: ../features/monorepos-and-workspaces.md#lint-a-single-workspace
-[26]: #enumerations
-[27]: #external-libraries
-[28]: ../guides/namespace-imports.md
-[29]: ../reference/cli#--include-libs
-[30]: #class-members
-[31]: ../reference/configuration.md#ignoreexportsusedinfile
-[32]: ../reference/jsdoc-tsdoc-tags.md
-[33]: ../reference/configuration.md#includeentryexports
-[34]: ../guides/issue-reproduction
-[35]: https://discord.gg/r5uXTtbTpc
+[24]: ../features/monorepos-and-workspaces.md#lint-a-single-workspace
+[25]: #enumerations
+[26]: #external-libraries
+[27]: ../guides/namespace-imports.md
+[28]: ../reference/cli#--include-libs
+[29]: #class-members
+[30]: ../reference/configuration.md#ignoreexportsusedinfile
+[31]: ../reference/jsdoc-tsdoc-tags.md
+[32]: ../reference/configuration.md#includeentryexports
+[33]: ../guides/issue-reproduction
+[34]: https://discord.gg/r5uXTtbTpc