@knip/mcp 0.0.3 → 0.0.4

package/docs/docs/reference/plugins.md

@@ -1,238 +0,0 @@
----
-title: Plugins (114)
-tableOfContents: false
----
-
-:::section{.columns.min200}
-
-- [Angular][1]
-- [Astro][2]
-- [Ava][3]
-- [Babel][4]
-- [Biome][5]
-- [bumpp][6]
-- [Bun][7]
-- [c8][8]
-- [Capacitor][9]
-- [Changelogen][10]
-- [Changelogithub][11]
-- [Changesets][12]
-- [Commitizen][13]
-- [commitlint][14]
-- [Convex][15]
-- [create-typescript-app][16]
-- [CSpell][17]
-- [Cucumber][18]
-- [Cypress][19]
-- [dependency-cruiser][20]
-- [Docusaurus][21]
-- [dotenv][22]
-- [Drizzle][23]
-- [Eleventy][24]
-- [ESLint][25]
-- [Expo][26]
-- [Gatsby][27]
-- [GitHub Action][28]
-- [GitHub Actions][29]
-- [glob][30]
-- [GraphQL Codegen][31]
-- [Hardhat][32]
-- [husky][33]
-- [i18next Parser][34]
-- [Jest][35]
-- [Karma][36]
-- [Ladle][37]
-- [Lefthook][38]
-- [lint-staged][39]
-- [LintHTML][40]
-- [lockfile-lint][41]
-- [Lost Pixel][42]
-- [markdownlint][43]
-- [Metro][44]
-- [Mocha][45]
-- [moonrepo][46]
-- [Mock Service Worker][47]
-- [Nano Staged][48]
-- [Nest][49]
-- [Netlify][50]
-- [Next.js][51]
-- [Node.js][52]
-- [node-modules-inspector][53]
-- [nodemon][54]
-- [npm-package-json-lint][55]
-- [Nuxt][56]
-- [Nx][57]
-- [nyc][58]
-- [oclif][59]
-- [Oxlint][60]
-- [Playwright][61]
-- [Playwright for components][62]
-- [playwright-test][63]
-- [Plop][64]
-- [pnpm][65]
-- [PostCSS][66]
-- [Preconstruct][67]
-- [Prettier][68]
-- [Prisma][69]
-- [React Cosmos][70]
-- [React Router][71]
-- [Relay][72]
-- [Release It!][73]
-- [Remark][74]
-- [Remix][75]
-- [Rollup][76]
-- [Rsbuild][77]
-- [Rslib][78]
-- [Rspack][79]
-- [Rstest][80]
-- [Semantic Release][81]
-- [Sentry][82]
-- [simple-git-hooks][83]
-- [size-limit][84]
-- [SST][85]
-- [Starlight][86]
-- [Storybook][87]
-- [Stryker][88]
-- [Stylelint][89]
-- [Svelte][90]
-- [SVGO][91]
-- [Syncpack][92]
-- [Tailwind][93]
-- [Travis CI][94]
-- [ts-node][95]
-- [tsdown][96]
-- [tsup][97]
-- [tsx][98]
-- [TypeDoc][99]
-- [TypeScript][100]
-- [unbuild][101]
-- [UnoCSS][102]
-- [Vercel OG][103]
-- [Vike][104]
-- [Vite][105]
-- [Vitest][106]
-- [Vue][107]
-- [WebdriverIO][108]
-- [webpack][109]
-- [Wireit][110]
-- [Wrangler][111]
-- [xo][112]
-- [Yarn][113]
-- [yorkie][114]
-
-:::
-
-[1]: /reference/plugins/angular 'Angular'
-[2]: /reference/plugins/astro 'Astro'
-[3]: /reference/plugins/ava 'Ava'
-[4]: /reference/plugins/babel 'Babel'
-[5]: /reference/plugins/biome 'Biome'
-[6]: /reference/plugins/bumpp 'bumpp'
-[7]: /reference/plugins/bun 'Bun'
-[8]: /reference/plugins/c8 'c8'
-[9]: /reference/plugins/capacitor 'Capacitor'
-[10]: /reference/plugins/changelogen 'Changelogen'
-[11]: /reference/plugins/changelogithub 'Changelogithub'
-[12]: /reference/plugins/changesets 'Changesets'
-[13]: /reference/plugins/commitizen 'Commitizen'
-[14]: /reference/plugins/commitlint 'commitlint'
-[15]: /reference/plugins/convex 'Convex'
-[16]: /reference/plugins/create-typescript-app 'create-typescript-app'
-[17]: /reference/plugins/cspell 'CSpell'
-[18]: /reference/plugins/cucumber 'Cucumber'
-[19]: /reference/plugins/cypress 'Cypress'
-[20]: /reference/plugins/dependency-cruiser 'dependency-cruiser'
-[21]: /reference/plugins/docusaurus 'Docusaurus'
-[22]: /reference/plugins/dotenv 'dotenv'
-[23]: /reference/plugins/drizzle 'Drizzle'
-[24]: /reference/plugins/eleventy 'Eleventy'
-[25]: /reference/plugins/eslint 'ESLint'
-[26]: /reference/plugins/expo 'Expo'
-[27]: /reference/plugins/gatsby 'Gatsby'
-[28]: /reference/plugins/github-action 'GitHub Action'
-[29]: /reference/plugins/github-actions 'GitHub Actions'
-[30]: /reference/plugins/glob 'glob'
-[31]: /reference/plugins/graphql-codegen 'GraphQL Codegen'
-[32]: /reference/plugins/hardhat 'Hardhat'
-[33]: /reference/plugins/husky 'husky'
-[34]: /reference/plugins/i18next-parser 'i18next Parser'
-[35]: /reference/plugins/jest 'Jest'
-[36]: /reference/plugins/karma 'Karma'
-[37]: /reference/plugins/ladle 'Ladle'
-[38]: /reference/plugins/lefthook 'Lefthook'
-[39]: /reference/plugins/lint-staged 'lint-staged'
-[40]: /reference/plugins/linthtml 'LintHTML'
-[41]: /reference/plugins/lockfile-lint 'lockfile-lint'
-[42]: /reference/plugins/lost-pixel 'Lost Pixel'
-[43]: /reference/plugins/markdownlint 'markdownlint'
-[44]: /reference/plugins/metro 'Metro'
-[45]: /reference/plugins/mocha 'Mocha'
-[46]: /reference/plugins/moonrepo 'moonrepo'
-[47]: /reference/plugins/msw 'Mock Service Worker'
-[48]: /reference/plugins/nano-staged 'Nano Staged'
-[49]: /reference/plugins/nest 'Nest'
-[50]: /reference/plugins/netlify 'Netlify'
-[51]: /reference/plugins/next 'Next.js'
-[52]: /reference/plugins/node 'Node.js'
-[53]: /reference/plugins/node-modules-inspector 'node-modules-inspector'
-[54]: /reference/plugins/nodemon 'nodemon'
-[55]: /reference/plugins/npm-package-json-lint 'npm-package-json-lint'
-[56]: /reference/plugins/nuxt 'Nuxt'
-[57]: /reference/plugins/nx 'Nx'
-[58]: /reference/plugins/nyc 'nyc'
-[59]: /reference/plugins/oclif 'oclif'
-[60]: /reference/plugins/oxlint 'Oxlint'
-[61]: /reference/plugins/playwright 'Playwright'
-[62]: /reference/plugins/playwright-ct 'Playwright for components'
-[63]: /reference/plugins/playwright-test 'playwright-test'
-[64]: /reference/plugins/plop 'Plop'
-[65]: /reference/plugins/pnpm 'pnpm'
-[66]: /reference/plugins/postcss 'PostCSS'
-[67]: /reference/plugins/preconstruct 'Preconstruct'
-[68]: /reference/plugins/prettier 'Prettier'
-[69]: /reference/plugins/prisma 'Prisma'
-[70]: /reference/plugins/react-cosmos 'React Cosmos'
-[71]: /reference/plugins/react-router 'React Router'
-[72]: /reference/plugins/relay 'Relay'
-[73]: /reference/plugins/release-it 'Release It!'
-[74]: /reference/plugins/remark 'Remark'
-[75]: /reference/plugins/remix 'Remix'
-[76]: /reference/plugins/rollup 'Rollup'
-[77]: /reference/plugins/rsbuild 'Rsbuild'
-[78]: /reference/plugins/rslib 'Rslib'
-[79]: /reference/plugins/rspack 'Rspack'
-[80]: /reference/plugins/rstest 'Rstest'
-[81]: /reference/plugins/semantic-release 'Semantic Release'
-[82]: /reference/plugins/sentry 'Sentry'
-[83]: /reference/plugins/simple-git-hooks 'simple-git-hooks'
-[84]: /reference/plugins/size-limit 'size-limit'
-[85]: /reference/plugins/sst 'SST'
-[86]: /reference/plugins/starlight 'Starlight'
-[87]: /reference/plugins/storybook 'Storybook'
-[88]: /reference/plugins/stryker 'Stryker'
-[89]: /reference/plugins/stylelint 'Stylelint'
-[90]: /reference/plugins/svelte 'Svelte'
-[91]: /reference/plugins/svgo 'SVGO'
-[92]: /reference/plugins/syncpack 'Syncpack'
-[93]: /reference/plugins/tailwind 'Tailwind'
-[94]: /reference/plugins/travis 'Travis CI'
-[95]: /reference/plugins/ts-node 'ts-node'
-[96]: /reference/plugins/tsdown 'tsdown'
-[97]: /reference/plugins/tsup 'tsup'
-[98]: /reference/plugins/tsx 'tsx'
-[99]: /reference/plugins/typedoc 'TypeDoc'
-[100]: /reference/plugins/typescript 'TypeScript'
-[101]: /reference/plugins/unbuild 'unbuild'
-[102]: /reference/plugins/unocss 'UnoCSS'
-[103]: /reference/plugins/vercel-og 'Vercel OG'
-[104]: /reference/plugins/vike 'Vike'
-[105]: /reference/plugins/vite 'Vite'
-[106]: /reference/plugins/vitest 'Vitest'
-[107]: /reference/plugins/vue 'Vue'
-[108]: /reference/plugins/webdriver-io 'WebdriverIO'
-[109]: /reference/plugins/webpack 'webpack'
-[110]: /reference/plugins/wireit 'Wireit'
-[111]: /reference/plugins/wrangler 'Wrangler'
-[112]: /reference/plugins/xo 'xo'
-[113]: /reference/plugins/yarn 'Yarn'
-[114]: /reference/plugins/yorkie 'yorkie'

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

@@ -1,46 +0,0 @@
----
-title: Related Tooling
----
-
-This is an overview of related tooling for features Knip does not support.
-
-## Unused variables
-
-Knip doesn't look for unused variables within a file. The focus is on exported
-and imported values and types across files.
-
-Use [ESLint][1], [Biome][2] or [oxlint][3] to find unused variables within
-files.
-
-Use [remove-unused-vars][4] to remove unused code within files, but in a more
-valiant way. Using input from any of the above linters, it actually removes a
-lot more unused code. This pairs great with Knip.
-
-## Unused properties
-
-Knip does not yet support finding unused members of types, interfaces and
-objects. This includes returned objects from exported functions and objects
-passed as React component props.
-
-Knip does support finding unused members of enums and classes, and exported
-values and types on imported namespaces.
-
-## Circular dependencies
-
-Knip has no issues with circular dependencies, and does not report them. Tools
-that do support this include [DPDM][5], [Madge][6] and [skott][7].
-
-## Cleanup
-
-The [e18e.dev][8] website and in particular the [Cleanup][9] section is a great
-resource when dealing with technical debt.
-
-[1]: https://eslint.org
-[2]: https://biomejs.dev/linter/
-[3]: https://oxc.rs/docs/guide/usage/linter.html
-[4]: https://github.com/webpro-nl/remove-unused-vars
-[5]: https://github.com/acrazing/dpdm
-[6]: https://github.com/pahen/madge
-[7]: https://github.com/antoine-coulon/skott
-[8]: https://e18e.dev
-[9]: https://e18e.dev/guide/cleanup.html

package/docs/docs/sponsors.mdx

@@ -1,65 +0,0 @@
----
-title: 'Become a sponsor!'
-template: splash
----
-
-import StarlightPage from '@astrojs/starlight/components/StarlightPage.astro';
-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}
-
-Knip is a powerful tool that helps thousands of developers keep their JavaScript
-and TypeScript projects lean and maintainable. Knip saves teams valuable time
-and resources.
-
-Building and maintaining Knip has been, and remains, a lot of work. Supportive
-resources allow me to focus on maintenance and development of Knip, which is
-[relied upon][1] [by many][2] in the JavaScript community. Please consider
-supporting the project! The following platforms are available to support Knip:
-
-- [GitHub Sponsors][3]
-- [OpenCollective][4]
-
-You or your company logo with a backlink to your website will be added to this
-page if you decide to support the project on an ongoing basis. Eternal gratitude
-to the companies and people supporting the project!
-
-:::
-
-<SponsorsComponent showAll={true} />
-
-## Monthly Overview
-
-Overview of gross GitHub and OpenCollective sponsorships and invoices, starting
-from the moment the project openly asked for support. Actual development started
-one year before that.
-
-<SponsorsChart />
-
-- The monthly aggregated average over the charted period is $507.
-- The monthly recurring average without one-time payments is $331.
-- 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].
-
-## Trusted by the world's best software teams
-
-<section class="columns min300">
-  <Projects />
-</section>
-
-## Don't just take our word for it
-
-<Posts />
-
-[1]: #trusted-by-the-worlds-best-software-teams
-[2]: https://github.com/webpro-nl/knip/network/dependents
-[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
-[7]: https://try.venz.dev

package/docs/docs/typescript/unused-dependencies.md

@@ -1,86 +0,0 @@
----
-title: Unused dependencies
-description: Find and remove unused dependencies with Knip
-prev: false
-next: false
----
-
-One of Knip's core features is finding unused dependencies in your JavaScript
-and TypeScript projects. And it comes with many more features to remove clutter
-and keep your projects in great shape.
-
-## Why are unused dependencies a problem?
-
-Having unused dependencies in your `package.json` is an issue for various
-reasons:
-
-- They might end up in the final production bundle, increasing size and load
-  times for end users.
-- They waste space in `node_modules` and add to the installation time of the
-  project.
-- They slow down tooling such as linters and bundlers that analyze dependencies.
-- They are confusing and noisy in `package.json`.
-- They cause unnecessary extra work when managing and upgrading dependencies.
-- They can cause version conflicts with other dependencies in use.
-- They can cause false security alerts.
-- They might have restrictive licenses and make your project subject to theirs.
-- They usually come with transitive dependencies that have the same issues.
-
-## How do I find unused dependencies?
-
-Use Knip to find and remove unused dependencies. It also finds dependencies that
-are missing in `package.json` and has a lot more features to keep your
-JavaScript and TypeScript projects tidy.
-
-It's easy to [get started][1] and make package management easier and more fun!
-
-<div style="display: flex; justify-content: center; margin: 4rem auto;">
-  <img src="/logo.svg" alt="Logo of Knip, to find unused dependencies, exports and files" class="logo-border" />
-</div>
-
-## How does Knip identify unused dependencies?
-
-Knip works by analyzing `package.json` files, source code and configuration
-files for other tooling in the project to find unused and missing dependencies.
-Knip has many heuristics, [plugins][2] and [compilers][3] to fully automate the
-process.
-
-## Can Knip remove unused dependencies?
-
-Yes, Knip can automatically remove unused dependencies installed by a package
-manager like npm or pnpm for you. Add the `--fix` argument to [auto-fix][4] and
-remove unused dependencies from `package.json`.
-
-## Can Knip detect missing dependencies?
-
-Yes, Knip detects missing dependencies. It analyzes `package.json` files, and
-reports packages that are missing. They should be added to `package.json` to
-avoid relying on transitive dependencies that can cause version mismatches and
-breakage.
-
-## Does Knip work with monorepos?
-
-Yes, Knip has first-class support for [monorepos and workspaces][5]. It analyzes
-all workspaces in the project and understands their relationship.
-
-For instance, if a dependency is listed in the root `package.json` it does not
-need to be listed in other workspaces. Except if you enable `--strict` checking.
-
-## Does Knip separate dependencies and devDependencies?
-
-Yes, Knip understands the difference between dependencies and devDependencies.
-It has a [production mode][6] to focus on production code only and find dead
-code and dependencies that would otherwise only be referenced by tests and other
-tooling. This allows you to remove both unused exported code and their tests.
-
-## Does Knip work with my package manager?
-
-Yes, Knip works with any package manager: npm, pnpm, Bun and Yarn are all
-supported. It's easy to [get started][1] with any package manager.
-
-[1]: ../overview/getting-started.mdx
-[2]: ../reference/plugins.md
-[3]: ../features/compilers.md
-[4]: ../features/auto-fix.mdx
-[5]: ../features/monorepos-and-workspaces.md
-[6]: ../features/production-mode.md

package/docs/docs/typescript/unused-exports.md

@@ -1,87 +0,0 @@
----
-title: Unused exports
-description: Find and remove unused exports with Knip
-prev: false
-next: false
----
-
-Finding unused exports in your JavaScript and TypeScript projects is one of
-Knip's core features. And it comes with even more features to identify and
-remove clutter to keep your projects in great shape.
-
-## Why are unused exports a problem?
-
-Having unused exports in your codebase is problematic for several reasons:
-
-- They increase bundle sizes if not properly eliminated by tree-shaking.
-- They clutter the codebase and make it harder to navigate and understand.
-- They mislead developers into thinking certain code is used when it's not.
-- They make refactoring and maintaining the codebase more difficult.
-- They slow down tooling that analyze the codebase, such as bundlers, linters
-  and type checkers.
-- They may represent dead code that is no longer needed but hasn't been cleaned
-  up.
-
-## How do I find unused exports?
-
-Knip is a powerful tool that can help you find and remove unused exports in your
-JavaScript and TypeScript projects. It analyzes the codebase, identifies exports
-that are not imported anywhere, and reports them.
-
-[Get started and install Knip][1] to run it on your project. Knip will scan your
-files and provide a detailed report of unused exports, and much more.
-
-<div style="display: flex; justify-content: center; margin: 4rem auto;">
-  <img src="/logo.svg" alt="Logo of Knip, to find unused dependencies, exports and files" class="logo-border" />
-</div>
-
-## How does Knip identify unused exports?
-
-Knip performs both static and dynamic analysis to determine which exports are
-actually being used in your codebase. It looks at import statements, export
-usage, and [a lot more code patterns][2] to identify unused exports.
-
-Knip supports JavaScript and TypeScript projects, and handles both [CommonJS][3]
-and ES Modules syntax.
-
-## Can Knip remove unused exports?
-
-Yes, Knip not only finds unused exports but can also remove them for you. Run
-Knip with the `--fix` flag to enable [the auto-fix feature][4], and it will
-modify your source code and remove the unused exports.
-
-It's always recommended to review the changes made by Knip before committing
-them to ensure no unintended modifications were made.
-
-## Can Knip handle large codebases?
-
-Absolutely. Knip supports [monorepos with workspaces][5] and utilizes [workspace
-sharing][6] to efficiently analyze large monorepos. This makes it easier and
-more fun to manage and optimize large multi-package projects.
-
-## Does Knip work with my favorite editor or IDE?
-
-Knip is a command-line tool that runs independently of your editor or IDE.
-However, if you run Knip inside an integrated IDE terminal, the report contains
-file names and positions in a format IDEs like VS Code and WebStorm understand
-to easily navigate around.
-
-## How is Knip different from ESLint for finding unused exports?
-
-While linters like ESLint can find unused variables and imports within
-individual files, Knip analyzes the entire project to determine which exports
-are actually unused. By building [a comprehensive module graph][7], Knip
-identifies exports that are not imported or used anywhere in the codebase. This
-allows Knip to catch unused exports and dead code that ESLint and other linters
-would miss.
-
-Also see [Why isn't Knip an ESLint plugin?][8]
-
-[1]: ../overview/getting-started.mdx
-[2]: ../reference/faq.md#what-does-knip-look-for-in-source-files
-[3]: ../guides/working-with-commonjs.md
-[4]: ../features/auto-fix.mdx
-[5]: ../features/monorepos-and-workspaces.md
-[6]: ../guides/performance.md#workspace-sharing
-[7]: ../reference/faq.md#whats-in-the-graphs
-[8]: ../reference/faq.md#why-isnt-knip-an-eslint-plugin