Migrate to @babel/eslint-parser #263
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I ran into an issue with eslint which led me to the solution - which is to use
@babel/eslint-parserinstead ofbabel-eslintwhich is deprecated.Note that I had to also set
BABEL_ENV = developmentin the script commandhttps://babeljs.io/blog/2020/07/13/the-state-of-babel-eslint
This fixes the issue when I run the linter locally, but the linter bot fails because our library doesn't have
@babel/eslint-parserand@babel/eslint-plugin@kadamwhite how could I test this to make it more likely to get merged without breaking anything?