Add explicit support for ESLint 6.0.0 #15974
Merged
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
Preemptively update tests wrt 'parser' requiring an absolute path rather than a package name, even though the project is still using ESLint 4. Fixes #15971
|
No significant bundle size changes to report. Generated by 🚫 dangerJS |
Collaborator
|
Thanks. |
rickhanlonii
pushed a commit
to rickhanlonii/react
that referenced
this pull request
Jun 25, 2019
Preemptively update tests wrt 'parser' requiring an absolute path rather than a package name, even though the project is still using ESLint 4. Fixes facebook#15971
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Preemptively update tests wrt 'parser' requiring an absolute path rather than a package name, even though the project is still using ESLint 4.
Tested locally by upgrading eslint (and all
eslint-*dependencies) to their latest versions (usingyarn upgrade-interactive --latest) and then runningyarn test. Without the change to the tests, they expectedly failed due to theparseroption not being an absolute path; with the change to the tests, they all pass.Fixes #15971