sf-mcp-server: mcp-provider-lwc-experts uses incompatible eslintrc
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
### Summary
When building `sf-mcp-server` from source i.e. in homebrew (see https://github.com/Homebrew/homebrew-core/pull/269663 and https://github.com/Homebrew/homebrew-core/pull/269614), we are provided with an error regarding the usage of deprecated eslintrc stuff, inside `mcp-provider-lwc-experts`. This error basically means, that you use eslintrc but also use a new version of eslint that deprecated eslintrc.
This can be fixed by moving to flat eslint config inside `mcp-provider-lwc-experts` and or remove eslint completely from production dependencies.
### Steps To Reproduce
download the latest `sf-mcp-server` package from npm, and build from source.
Run the resulting mcp server file inside the bin folder.
Also you can replicate by manually running the build from this pr https://github.com/Homebrew/homebrew-core/pull/269614
### Expected result
no error
### Actual result
```
AccessibilityVisionExpert: no reviewers loaded for maturity level >= GA
Error: Invalid Options:
- Unknown options: reportUnusedDisableDirectives, useEslintrc
- 'reportUnusedDisableDirectives' has been removed. Please use the
'overrideConfig.linterOptions.reportUnusedDisableDirectives' option
instead.
Code: ESLINT_INVALID_OPTIONS
```
### Environment details
- Salesforce DX MCP Server version (run `npx --offline @salesforce/mcp --version`)
- 26.9
- MCP Client (A4D, Copilot, Cursor, etc)
- n/a
- LLM Model used (GPT-4.1, Claude Sonnet 4, ect)
- n/a
Contributor guide
Research direction
Start by reproducing the source build described in the issue and locating the ESLint configuration and production dependency inside mcp-provider-lwc-experts. Check the generated server in the bin folder and verify that running the built MCP server no longer reports deprecated eslintrc options or ESLINT_INVALID_OPTIONS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100