The prop value with an expression type of JSXFragment could not be resolved
See original GitHub issueHi,
I got this error while running ESLint on our code-base. Not sure where it is coming from though.
The prop value with an expression type of JSXFragment could not be resolved. Please file an issue to get this fixed immediately.
@typescript-eslint/eslint-plugin: 5.18.0
@typescript-eslint/parser: 5.18.0
eslint: 8.12.0
jsx-ast-utils: 3.2.1
node: v16.8.0
Hope this helps to fix the issue.
Issue Analytics
- State:
- Created a year ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
The prop value with an expression type of JSXFragment could ...
The prop value with an expression type of JSXFragment could not be resolved. Please file issue to get this fixed immediately. [eslint-fix] ...
Read more >I am getting this error: The prop value with an expression type ...
I am getting this error: The prop value with an expression type of Chain Expression could not be resolved. Please file is Failed...
Read more >jsx-ast-utils | Yarn - Package Manager
Returns the JSXAttribute itself or undefined, indicating the prop is not present on the ... to expression types to handle recursively extracting prop...
Read more >TSConfig Reference - Docs on every TSConfig option
An error occurs if any of the files can't be found. ... Raise error on 'this' expressions with an implied 'any' type. ......
Read more >eslint-plugin-react @ 7.10.0 .. 7.12.4 - Package Diff
+* [`prop-types`][]: avoid further crashes from nonexistent nodes in ... @returns {ASTNode|null} Return null if the value could not be resolved, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve created reproduction repo https://github.com/ondrejsevcik/jsx-fragment-issue-repo
when you run
npm run lint
you should run into that issue as well. Hopefully this helps.Thank you for a quick fix 👍🏽