fix(@roots/bud-eslint) use @babel/eslint-parser #892
Merged
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.
babel-eslint
to@babel/eslint-parser
.@roots/sage/eslint-config
for use in theme.@retlehs next sage release will need to have eslint configuration updated to:
I think this is the way to go. by exporting a base config further changes to the base will not need to be manually tracked by theme consumers. everything remains fully overridable so there is really very little trade off outside of a reduction of transparency. I think that's a good trade for most people using Sage (and for us as maintainers).
Dependencies