Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(rule-tester): fix parser fallback logic #7754

Merged
merged 1 commit into from
Oct 17, 2023
Merged

fix(rule-tester): fix parser fallback logic #7754

merged 1 commit into from
Oct 17, 2023

Commits on Oct 16, 2023

  1. fix(rule-tester): fix parser fallback logic 

    The docs at https://typescript-eslint.io/packages/rule-tester/#type-aware-testing
show that for type-aware rule testing `parserOptions` needs to be
specified. However, like shown in the docs, when `parser` is omitted
then an error: "The first argument to require.resolve must be a string.
Received null or undefined" is thrown due to a bug in `parser` fallback
behavior.
    @rriski
    rriski committed Oct 16, 2023
    Configuration menu
    Copy the full SHA
    e11c0b5 View commit details
    Browse the repository at this point in the history