New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: remove moduleResolver API #6609
Conversation
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## v6 #6609 +/- ##
==========================================
- Coverage 87.47% 87.40% -0.07%
==========================================
Files 365 365
Lines 12519 12508 -11
Branches 3697 3694 -3
==========================================
- Hits 10951 10933 -18
- Misses 1205 1213 +8
+ Partials 363 362 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔪 🔪 🔪
BREAKING CHANGE:
Removes
parserOptions.moduleResolver
.PR Checklist
Overview
As we discussed in the thread - we're removing this API.
We don't have any evidence that it's widely used and there is a pretty significant maintenance burden to keep it.