-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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.
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
The prop value with an expression type of SequenceExpression could not be resolved. Please file issue to get this fixed immediately. #3120
Comments
I meant yarn check-all I tried upgrading eslint. No help! |
jsx-eslint/jsx-ast-utils#95 could be the issue blocking. |
jsx-eslint/jsx-ast-utils#101 was merged & should fix this. |
@rrhg do you want to submit the PR to upgrade? |
I can try. If someone could provide some guidance that would be great. Thanks. |
@rrhg first step would be to figure out which dependency is using it and get that package to publish an upgraded version with the fix, then upgrade the version we use. |
Did some research & if I understand correctly, the 2 dependencies using it are eslint-plugin-react & eslint-plugin-jsx-a11y. eslint-plugin-react has a newer release tag (v7.21.4) that updated jsx-ast-utils to 3.0.0 & should fix this. But for eslint-plugin-jsx-a11y, we have to wait for an active branch (v6.4.0) to be merged. Apparently it should be ready soon. |
Thanks for looking into it @rrhg! |
Please update this thread if this already fixed. thanks |
These updates fix issue reactjs#3120. The real problem was in jsx-ast-utils which is a dependency of both eslint-plugin-react & eslint-plugin-jsx-a11y
1.Install [email protected] fix it |
Merged the fix, please let us know if this is still an issue after pulling and re-running |
you need to update react-scripts to solve this problem in package.json :
|
Not work |
I was just contributing to the docs a few minutes ago and after running
got this warning
"The prop value with an expression type of SequenceExpression could not be resolved. Please file issue to get this fixed immediately." .
Thought I'd let you know.
The text was updated successfully, but these errors were encountered: