The prop value with an expression type of JSXEmptyExpression could not be resolved

[Ali-Waseer]

I am facing an issue while I building my react project.
The prop value with an expression type of JSXEmptyExpression could not be resolved. Please file an issue ( https://github.com/jsx-eslint/jsx-ast-utils/issues/new ) to get this fixed immediately

[ljharb]

Do you know what code is causing this error?

[Ali-Waseer]

No, actually I just want to build my project and want it to live. The other developer working on same project and they are building and deploying their changes. They don't have such issues like this.

…

On Sun, 4 Jun 2023, 12:14 am Jordan Harband, ***@***.***> wrote: Do you know what code is causing this error? — Reply to this email directly, view it on GitHub <#128 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APBKTGOYLJJVER3JJPVTI4TXJOEJ5ANCNFSM6AAAAAAYZOCAP4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ljharb]

If you’re working on the same code with the same dep graph, you should get the same results.

i can’t help you fix your problem without more information.

[Ali-Waseer]

So, what you need more information?

…

On Sun, 4 Jun 2023, 12:24 am Jordan Harband, ***@***.***> wrote: If you’re working on the same code with the same dep graph, you should get the same results. i can’t help you fix your problem without more information. — Reply to this email directly, view it on GitHub <#128 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APBKTGIPU2QE5JLSO6TOYZTXJOFP7ANCNFSM6AAAAAAYZOCAP4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ljharb]

The code that’s causing the linting error, and confirmation that you’re using the latest version.

[happymvp]

@ljharb I got the issue from this empty onKeyDown handler in my case
<div onClick={handleCount} onKeyDown={} role="button" tabIndex={0}> {count} </div>

[ljharb]

@happymvp thanks - that's invalid jsx tho, i believe, so it shouldn't even parse. what eslint parser are you using?

[happymvp]

@happymvp thanks - that's invalid jsx tho, i believe, so it shouldn't even parse. what eslint parser are you using?

@typescript-eslint/parser

[ljharb]

hm, ok thanks, i'll see what i can do. i think there's a few places TS allows invalid JSX and this may be one of them.