Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[6.0.0-alpha.1] `RuleTester` fails tests if `parser` property is a package name #11728
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
Please show your full configuration:
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
What did you expect to happen?
What actually happened? Please include the actual, raw output from ESLint.
The test failed with "Parsers provided as strings to RuleTester must be absolute paths."
Are you willing to submit a pull request to fix this bug?
I think that
Also, the Migration Guide must describe this change.
referenced this issue
May 16, 2019
The current behavior is intentional because it's not clear where packages should be loaded from with
Thank you for the explanation.
But, my position is different. Because to use file paths for
I think that good design is "people can do the most popular use case easily, and can do rare cases with detailed way." I believe we should allow a package name and show a understandable error message for rare cases (E.g.,
This is an awareness that came from the failing CI build of
What is the direction we want to go?