Fix: Initialize ESLint for a TS project by analysing codebase (fixes… #13150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… #13149)
It fixes the issue where ESLint encounters an error while generating eslintrc file if you have a TypeScript project and you chose the option 'Inspect your JavaScript file(s)' from the initialization wizard.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
In
lib/init/autoconfig.js
I changed line #336 to setnewConfig.extends
to an array containingRECOMMENDED_CONFIG_NAME
instead of just setting it toRECOMMENDED_CONFIG_NAME
.Is there anything you'd like reviewers to focus on?
Nope