@knip/mcp 0.0.18 → 0.0.19

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

@@ -0,0 +1,146 @@
+---
+title: Configuration Hints
+---
+
+Knip emits configuration hints to help keep your configuration file tidy and
+reduce drift.
+
+They're warnings by default, not lint findings. But addressing the hints might
+improve results significantly. The hints on this page are sorted by
+impact/importance (most impactful first).
+
+Use [`--treat-config-hints-as-errors`][1] or [`treatConfigHintsAsErrors`][2] to
+make any configuration hint result in a non-zero exit code and fail CI.
+
+## Unconfigured projects
+
+Too many unused files in a single workspace-codebase, caused by a missing
+configuration file or incomplete configuration:
+
+```
+Create knip.json configuration file, and add entry and/or refine project files (42 unused files)
+```
+
+Or if you have a config file:
+
+```
+Add entry and/or refine project files (42 unused files)
+```
+
+**Solution**: Add and refine `entry` and/or `project` patterns.
+
+Related resources:
+
+- [Configuration][3]
+- [Monorepos & Workspaces][4]
+
+## Unconfigured workspaces
+
+Too many unused files in a monorepo, caused by a missing configuration file or
+incomplete configuration:
+
+```
+Create knip.json configuration file with workspaces["packages/app"] object (42 unused files)
+```
+
+Or if you have a config file:
+
+```
+Add entry and/or refine project files in workspaces["packages/app"] (42 unused files)
+```
+
+**Solution**: add a `workspaces` object to configuration. Add and refine `entry`
+and/or `project` patterns. For instance, the example message translates to
+configuration like this:
+
+```json
+{
+  "workspaces" {
+    "packages/app": {
+      "entry": ["src/App.tsx"],
+      "project": ["src/**/*.ts"]
+    }
+  }
+}
+```
+
+Related resources:
+
+- [Configuring Project Files][5]
+- [Monorepos & Workspaces][4]
+
+## Top-level entry/project
+
+In monorepos, Knip uses only `entry` and `project` under `workspaces`. The
+top-level keys with the same name are ignored.
+
+```
+Remove, or move unused top-level entry to one of "workspaces"
+Remove, or move unused top-level project to one of "workspaces"
+```
+
+**Solution**: Remove top-level `entry` and `project` keys, use these options in
+`workspaces` instead.
+
+```jsonc
+{
+  "entry": ["src/App.tsx"], // move entry/project from here... ↴
+  "project": ["src/**/*.ts"],
+  "workspaces": {
+    ".": {
+      "entry": ["src/App.tsx"], // ...to the correct workspace(s) ↲
+      "project": ["src/**/*.ts"],
+    },
+  },
+}
+```
+
+## Unused entry in ignore group
+
+An entry of an ignore list is no longer needed, remove it.
+
+```
+Remove from ignoreWorkspaces
+Remove from ignoreDependencies
+Remove from ignoreBinaries
+Remove from ignoreUnresolved
+```
+
+**Solution**: Remove the entry from the array.
+
+## Useless patterns
+
+A glob pattern in `entry` or `project` does not match any files.
+
+```
+Refine entry pattern (no matches)
+Refine project pattern (no matches)
+```
+
+**Solution**: Refine or remove the `entry` or `project` entry.
+
+## Redundant patterns
+
+A glob/pattern is redundant, because it's already covered by defaults or added
+by an enabled plugin.
+
+```
+Remove redundant entry pattern
+Remove redundant project pattern
+```
+
+**Solution**: Remove the `entry` or `project` entry.
+
+## Missing package entry file
+
+```
+Package entry file not found
+```
+
+**Solution**: Refine or remove the entry in `package.json`.
+
+[1]: ./cli.md#--treat-config-hints-as-errors
+[2]: ./configuration.md#treatconfighintsaserrors
+[3]: ../overview/configuration.md
+[4]: ../features/monorepos-and-workspaces.md
+[5]: ../guides/configuring-project-files.md

package/src/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`
@@ -198,17 +205,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 +284,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 +414,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 +425,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/reference/faq.md

@@ -38,26 +38,24 @@ File-oriented linters like ESLint are complementary to Knip.
 ### Isn't tree-shaking enough?
 
 In short: no. They share an important goal: improve UX by removing unused code.
-The main takeaway here is that tree-shaking and Knip are different and
-complementary tools.
+But tree-shaking and Knip are different and complementary tools.
 
 Tree-shaking is a build or compile-time activity to reduce production bundle
 size. It typically operates on bundled production code, which might include
-external/third-party code. An optimization in the build process, "out of your
-hands".
+external/third-party code. A build time optimization and "out of your hands".
 
-On the other hand, Knip is a project linter that should be part of the QA phase.
-It lints, reports and fixes only your own source code. Moreover, in contrast
-with other linters, focuses on inter-file dependencies, so dead code within a
-file may not be caught by Knip.
+On the other hand, Knip is a project linter that should be part of the
+development and QA phase. It lints, reports and fixes only your own source code.
+Moreover, in contrast with other linters, focuses on inter-file dependencies, so
+dead code within a file may not be caught by Knip.
 
-Issues reported by the linter are then for you to handle (except for everything
-that Knip [auto-fixes][1] for you).
+Issues reported by the linter are for you to handle and review.
 
 Besides those differences, Knip has a broader scope:
 
-- Improve DX (see [less is more][2]).
-- Include non-production code and dependencies in the process by default.
+- Improve DX (see [less is more][1]).
+- Unless using [production mode][2], also lint all source code like tests,
+  scripts and Storybook stories.
 - Handle more [types of issues][3] (such as unlisted dependencies).
 
 ## Synergy
@@ -306,28 +304,25 @@ dependencies, the [`--include-libs ` flag][4] will trigger the same.
 
 Projects can use `compilerOptions.paths` to alias paths in other workspaces in
 the same monorepo. Knip doesn't understand those paths might represent internal
-workspaces and might report false positives. How we ended up here is a bit
-complicated, but a major reason is that Knip does it's job based on the
-workspace graph, while [workspaces are different from TypeScript programs][11]
-and [the workspace graph doesn't match TypeScript project structure][12].
+workspaces and might report false positives.
 
 The recommendation and best practice is to list such workspaces/dependencies in
 `package.json`, and import them as such. Other tooling should not have any
 issues with this standard approach either.
 
-Also see the example in [TypeScript path aliases in monorepos][13].
+Also see the example in [TypeScript path aliases in monorepos][11].
 
 ### What's up with that configurable `tsconfig.json` location?
 
 There's a difference between `--tsConfig [file]` as a CLI argument and the
 `typescript.config` option in Knip configuration.
 
-The [`--tsConfig [file]` option][14] is used to provide an alternative location
+The [`--tsConfig [file]` option][12] is used to provide an alternative location
 for the default root `tsconfig.json` file. Relevant `compilerOptions` include
 `paths` and `moduleResolution`. This setting is only available at the root
 level.
 
-On the other hand, the [`config` option of the plugin][15] can be set per
+On the other hand, the [`config` option of the plugin][13] can be set per
 workspace. The TypeScript plugin extracts referenced external dependencies such
 as those in `extends`, `compilerOptions.types` and JSX settings:
 
@@ -351,7 +346,7 @@ From this example, Knip can determine whether the `@tsconfig/node20` and
   for `tsconfig.json` can be set per workspace.
 - In case path aliases from `compilerOptions.paths` aren't picked up by Knip,
   either use `--tsConfig [file]` to target a different `tsconfig.json`, or
-  manually add [paths][16] to the Knip configuration. The latter can be done per
+  manually add [paths][14] to the Knip configuration. The latter can be done per
   workspace.
 
 ## Compilers
@@ -374,7 +369,7 @@ other file types.
 Knip comes with basic "compilers" for a few common non-standard file types.
 They're not actual compilers, they're regular expressions only to extract import
 statements. Override the built-in Vue "compiler" with the real one in your
-project. Also see the answer to the previous question and [Compilers][17].
+project. Also see the answer to the previous question and [Compilers][15].
 
 ## Miscellaneous
 
@@ -394,7 +389,7 @@ Which mode should've been the default? They both have their merits:
   tooling, including most issues found in production mode. This mode has the
   most impact on DX, for the same reason.
 
-Also see [production mode][18].
+Also see [production mode][2].
 
 ### Why doesn't Knip have...?
 
@@ -408,34 +403,28 @@ 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,
-  duplicate exports, dead code, etc).
 - Replace dependencies for better performance and correctness, such as for shell
-  script parsing, module resolution and globbing with "unignores".
+  script parsing and globbing with "unignores".
 
 These are all interesting ideas, but most increase the API surface area, and all
 require more development efforts and maintenance. Time is limited and
-[sponsorships][19] currently don't cover - this can change though!
+[sponsorships][16] currently don't cover - this can change though!
 
-[1]: ../features/auto-fix.mdx
-[2]: ../explanations/why-use-knip.md#less-is-more
+[1]: ../explanations/why-use-knip.md#less-is-more
+[2]: ../features/production-mode.md
 [3]: ./issue-types.md
 [4]: ../guides/handling-issues.mdx#external-libraries
 [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
-[12]: #why-doesnt-knip-match-my-typescript-project-structure
-[13]: ../guides/handling-issues.mdx#typescript-path-aliases-in-monorepos
-[14]: ../reference/cli.md#--tsconfig-file
-[15]: ../explanations/plugins.md#configuration-files
-[16]: ../reference/configuration.md#paths
-[17]: ../features/compilers.md
-[18]: ../features/production-mode.md
-[19]: /sponsors
+[11]: ../guides/handling-issues.mdx#typescript-path-aliases-in-monorepos
+[12]: ../reference/cli.md#--tsconfig-file
+[13]: ../explanations/plugins.md#configuration-files
+[14]: ../reference/configuration.md#paths
+[15]: ../features/compilers.md
+[16]: /sponsors

package/src/docs/reference/integrations.md

@@ -0,0 +1,105 @@
+---
+title: Integrations
+---
+
+- [VS Code/VSX Extension][1]
+- [JetBrains Plugin][2]
+- [MCP Server][3]
+- [Language Server][4]
+
+## VS Code Extension
+
+The official VS Code extension provides a rich integration with the [Knip
+Language Server][4]:
+
+- **Diagnostics**: Inline warnings for unused dependencies, exports and files
+- **Hover Information**: Hover over exports to see import and usage locations
+- **Imports Tree View**: Direct links to implementations
+- **Exports Tree View**: Direct links to import and usage locations
+- **Contention Detection**: Warnings for circular dependencies, conflicts and
+  branched import chains
+- **Built-in MCP Server**: Automated configuration support for coding agents
+
+Find [Knip on the VS Code Marketplace][5] and find [Knip in the Open VSX
+Registry][6].
+
+See below for [screenshots][7].
+
+## JetBrains Plugin
+
+A community plugin is available for JetBrains IDEs including WebStorm, IntelliJ
+IDEA, and others. The plugin is powered by the [Knip Language Server][4] and
+provides diagnostics. Find [Knip on the JetBrains Marketplace][8].
+
+## MCP Server
+
+The standalone MCP Server enables coding agents to configure Knip automatically.
+Tell your agent to "configure knip" and it will use the available tools to
+create, analyze and optimize your `knip.json` configuration.
+
+The [Knip MCP Server][9] is available separately and built into the [Knip VS
+Code Extension][1].
+
+Start:
+
+```sh
+npx @knip/mcp
+```
+
+Note: The VS Code extension has this MCP Server built-in.
+
+## Language Server
+
+The IDE integrations are powered by the Knip Language Server. It builds the full
+module graph of your project and provides a session with a graph explorer. See
+the [Knip Language Server documentation][10] for more details and information on
+integrating Knip.
+
+## VS Code Extension Screenshots
+
+### Lint Findings
+
+![Lint Findings][11]
+
+### Imports & Exports
+
+![Hover over imports and exports][12]
+
+### Contention
+
+The IDE extension shows extra issues in the tree views like circular
+dependencies.
+
+#### Circular Dependencies
+
+![Circular Dependencies][13]
+
+#### Conflicts
+
+![Conflicts][14]
+
+#### Branching
+
+![Branching][15]
+
+### Settings
+
+![VS Code Extension Settings][16]
+
+[1]: #vs-code-extension
+[2]: #jetbrains-plugin
+[3]: #mcp-server
+[4]: #language-server
+[5]: https://marketplace.visualstudio.com/items?itemName=webpro.vscode-knip
+[6]: https://open-vsx.org/extension/webpro/vscode-knip
+[7]: #vs-code-extension-screenshots
+[8]: https://plugins.jetbrains.com/plugin/29765-knip
+[9]: https://www.npmjs.com/package/@knip/mcp
+[10]:
+  https://github.com/webpro-nl/knip/blob/main/packages/language-server/README.md
+[11]: /screenshots/editors-and-agents/diagnostics.webp
+[12]: /screenshots/editors-and-agents/imports-exports.webp
+[13]: /screenshots/editors-and-agents/circular-dependency.webp
+[14]: /screenshots/editors-and-agents/conflict.webp
+[15]: /screenshots/editors-and-agents/branch.webp
+[16]: /screenshots/editors-and-agents/vscode-extension-settings.webp

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

@@ -2,31 +2,50 @@
 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, missing path aliases, 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:
+
+- [Set path aliases][2] for "Cannot find module" errors
+- Set missing environment variable(s), potential solutions:
+  - Use a helper package like [dotenvx][3]
+  - `KEY=VAL knip`
+  - `node --env-file .env $(which knip)`
+- 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 +54,15 @@ 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).
+- Inject support with a module like `tsx`: `NODE_OPTIONS="--import tsx" knip`
+- Or `tsconfig-paths`: `NODE_OPTIONS="--import tsconfig-paths/register.js" knip`
+- Use Bun with [knip-bun][4].
+- See [exceptions from config files][5] for more potential workarounds.
 
 ## Nx Daemon
 
@@ -53,12 +72,15 @@ 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][6]:
 
 ```sh
 NX_DAEMON=false knip
 ```
 
-[1]: ./configuration.md#plugins
-[2]: ./cli.md#knip-bun
-[3]: https://nx.dev/concepts/nx-daemon#turning-it-off
+[1]: ../guides/handling-issues.mdx
+[2]: #path-aliases-in-config-files
+[3]: https://dotenvx.com/
+[4]: ./cli.md#knip-bun
+[5]: #exceptions-from-config-files
+[6]: https://nx.dev/concepts/nx-daemon#turning-it-off

package/src/docs/reference/plugins.md

@@ -1,5 +1,5 @@
 ---
-title: Plugins (123)
+title: Plugins (131)
 tableOfContents: false
 ---
 
@@ -7,6 +7,7 @@ tableOfContents: false
 - [Angular](/reference/plugins/angular "Angular")
 - [Astro](/reference/plugins/astro "Astro")
 - [Astro DB](/reference/plugins/astro-db "Astro DB")
+- [astro-og-canvas](/reference/plugins/astro-og-canvas "astro-og-canvas")
 - [Ava](/reference/plugins/ava "Ava")
 - [Babel](/reference/plugins/babel "Babel")
 - [Biome](/reference/plugins/biome "Biome")
@@ -32,6 +33,7 @@ tableOfContents: false
 - [Eleventy](/reference/plugins/eleventy "Eleventy")
 - [ESLint](/reference/plugins/eslint "ESLint")
 - [Expo](/reference/plugins/expo "Expo")
+- [Expressive Code](/reference/plugins/expressive-code "Expressive Code")
 - [Gatsby](/reference/plugins/gatsby "Gatsby")
 - [GitHub Action](/reference/plugins/github-action "GitHub Action")
 - [GitHub Actions](/reference/plugins/github-actions "GitHub Actions")
@@ -42,6 +44,7 @@ tableOfContents: false
 - [i18next Parser](/reference/plugins/i18next-parser "i18next Parser")
 - [Jest](/reference/plugins/jest "Jest")
 - [Karma](/reference/plugins/karma "Karma")
+- [Knex](/reference/plugins/knex "Knex")
 - [Ladle](/reference/plugins/ladle "Ladle")
 - [Lefthook](/reference/plugins/lefthook "Lefthook")
 - [lint-staged](/reference/plugins/lint-staged "lint-staged")
@@ -61,6 +64,7 @@ tableOfContents: false
 - [Next.js](/reference/plugins/next "Next.js")
 - [next-intl](/reference/plugins/next-intl "next-intl")
 - [Next.js MDX](/reference/plugins/next-mdx "Next.js MDX")
+- [Nitro](/reference/plugins/nitro "Nitro")
 - [Node.js](/reference/plugins/node "Node.js")
 - [node-modules-inspector](/reference/plugins/node-modules-inspector "node-modules-inspector")
 - [nodemon](/reference/plugins/nodemon "nodemon")
@@ -70,6 +74,7 @@ tableOfContents: false
 - [nyc](/reference/plugins/nyc "nyc")
 - [oclif](/reference/plugins/oclif "oclif")
 - [Oxlint](/reference/plugins/oxlint "Oxlint")
+- [Parcel](/reference/plugins/parcel "Parcel")
 - [Playwright](/reference/plugins/playwright "Playwright")
 - [Playwright for components](/reference/plugins/playwright-ct "Playwright for components")
 - [playwright-test](/reference/plugins/playwright-test "playwright-test")
@@ -100,11 +105,13 @@ tableOfContents: false
 - [Stryker](/reference/plugins/stryker "Stryker")
 - [Stylelint](/reference/plugins/stylelint "Stylelint")
 - [Svelte](/reference/plugins/svelte "Svelte")
+- [SvelteKit](/reference/plugins/sveltekit "SvelteKit")
 - [SVGO](/reference/plugins/svgo "SVGO")
 - [SVGR](/reference/plugins/svgr "SVGR")
 - [SWC](/reference/plugins/swc "SWC")
 - [Syncpack](/reference/plugins/syncpack "Syncpack")
 - [Tailwind](/reference/plugins/tailwind "Tailwind")
+- [TanStack Router](/reference/plugins/tanstack-router "TanStack Router")
 - [Taskfile](/reference/plugins/taskfile "Taskfile")
 - [Travis CI](/reference/plugins/travis "Travis CI")
 - [ts-node](/reference/plugins/ts-node "ts-node")
@@ -118,6 +125,7 @@ tableOfContents: false
 - [Vercel OG](/reference/plugins/vercel-og "Vercel OG")
 - [Vike](/reference/plugins/vike "Vike")
 - [Vite](/reference/plugins/vite "Vite")
+- [VitePress](/reference/plugins/vitepress "VitePress")
 - [Vitest](/reference/plugins/vitest "Vitest")
 - [Vue](/reference/plugins/vue "Vue")
 - [WebdriverIO](/reference/plugins/webdriver-io "WebdriverIO")

package/src/docs/reference/related-tooling.md

@@ -4,10 +4,10 @@ title: Related Tooling
 
 This is an overview of related tooling for features Knip does not support.
 
-## Unused variables
+## Unused imports & variables
 
-Knip doesn't look for unused variables within a file. The focus is on exported
-and imported values and types across files.
+Knip doesn't look for unused imports and variables within a file. The focus is
+on exported values and types across files.
 
 Use [ESLint][1], [Biome][2] or [oxlint][3] to find unused variables within
 files.

package/src/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}
 
@@ -40,8 +39,8 @@ 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 aggregated average over the charted period is $513.
+- The monthly recurring average without one-time payments is $350.
 - 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