Description
ESLint version
v9.26.0
What problem do you want to solve?
ESLint v9.26.0 introduces a built-in MCP server (#19592), which on its own is a brilliant feature! 👏
However, adding @modelcontextprotocol/sdk as a direct dependency of the core library package bloats the dependency graphs of users who don't use the MCP at all.
I noticed this when a seemingly routine pnpm up caused a +600 diff in the pnpm-lock.yaml. Sure enough, the culprit was @modelcontextprotocol/sdk.1
What do you think is the correct solution?
Spin off the MCP server as its own separate CLI package from the core ESLint CLI package.
Participation
- I am willing to submit a pull request for this change.
Additional comments
As I'd like to minimize the dependency surface of my projects, I consider this to be an essential refactor.
Footnotes
-
Here are the declared dependencies in the
package.json. ↩
Metadata
Metadata
Assignees
Labels
Type
Projects
Status