Chore: use espree.latestEcmaVersion in config-initializer #13157
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.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] 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
[x] Other, please explain:
Chore
What changes did you make? (Give an overview)
This is a small PR that utilizes
espree.latestEcmaVersion
in the config initializer so that we don't have to manually update this each time we add a new version to the parser.Is there anything you'd like reviewers to focus on?
This value will change as soon as we update to a version of Espree with a new supported
ecmaVersion
. Is that undesirable for any reason? Since the intention is to always use the latest version and since this is intended to only be used once by new users, I don't think this is an issue, but just wanted to check with the rest of the team.