How is this creating an error?
When I reload typescript server, this error goes away. But this keeps popping up over and over again throughout my codebase, and on others working on this same project as well. What is causing this? This is a fresh codebase in the T3-Stack, nothing weird has been done to it, just using default setup.
12 Replies
What are the steps you have done to research this on your own?
Checked if
createdResult
is in fact of type any
or not, which it is not. Not sure what more I can do to research this. I've also tried to google this issue to see if more people are finding a similar problem with this error, but to no avail.Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
You may need to provide a minimal viable Repro for debugging, could be an issue with tRPC and if that is the case it would need to be filed in the GitHub issues for tRPC.
https://stackoverflow.com/help/minimal-reproducible-example
Stack Overflow
How to create a Minimal, Reproducible Example - Help Center
Stack Overflow | The World’s Largest Online Community for Developers
I've tried to reproduce this issue numerous times, but it is insanely incosistant and the issue dissapears when reloading IDE/TS
What's your dev environment?
OS, Node version, IDE, etc..
@IntergalacticSurfer same question to you
Also experiencing this same issue and it can be very frustrating. I end up having to force the type by using
as
to resolve the error despite intellisense displaying the correct type.What's your setup too then?
Might be a bug with tRPC or Prisma
Used create t3 app about a week ago with all options enabled on Windows 10, Node 18.1, using VSC. I assume this is an eslint issue given that VSC's intellisense picked up on the correct type for me and restarting TS server would temporarily resolve the issue, but not completely sure
Node 18.1, Windows 10. Vsc/Webstorm
Node 18.1 arch linux. Vsc/webstorm
Node 18.1.windows 11. Vsc
Node 18.1. Fedora linux. Vsc
On a fresh create t3 app without any drastic changes to it.
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
Any updates on this from anybody?
Issue still persists