Replies: 8 comments 10 replies
-
can you show a reproduction please |
Beta Was this translation helpful? Give feedback.
-
Yes,
The main component is exported for use as an external library/component So I have two
I just figured out that I have the error when building in lib mode and with the plugin I'm going to dig deeper because I have the same issue on our UI library edifice-ui with two hooks :
I didn't have this error with v4.. |
Beta Was this translation helpful? Give feedback.
-
Just checking, So following, this info, doing this in vite config file is working in our UI library
but not working in our app |
Beta Was this translation helpful? Give feedback.
-
Having the same issue exporting inferred UseInfiniteQueryOptions and exporting hooks with mutations inside. |
Beta Was this translation helpful? Give feedback.
-
Having the same issue here. Tried upgrade latest typescript but couldn't help |
Beta Was this translation helpful? Give feedback.
-
I'm having the same issue after upgrading to v5. |
Beta Was this translation helpful? Give feedback.
-
Have anyone found a workaround for this on monorepos? I can't set |
Beta Was this translation helpful? Give feedback.
-
Had a lot of hooks in a package in my turbo repo Fix with "moduleResolution": "node" first, the error still remains in some of the hooks after updating my typescript to the latest version "typescript": "5.4.5", my package build successfully Thanks guys |
Beta Was this translation helpful? Give feedback.
-
Hello !
I have a bunch of queries and mutations exported as custom hooks:
Everything worked fine in v4 but after updating in v5, I have this typescript error :
To avoid the error, I have to declare the return type as below :
For info, I'm using React Query
5.8.4
.Any idea?
Beta Was this translation helpful? Give feedback.
All reactions