After upgrading to 11.0.0-next-beta.300, every request throws zod error
I didn't do anything but upgrading the trpc, and the error throws:
Rollbacking to
11.0.0-next-beta.178 solves.
15 Replies
hmm
could you check with
.299?it's the same
do i need to do binary divisions to find the problematic version lol
.297 still has problem
.260 still
.222 good
.240 good
i just tried upgrading to
.300 myself on a massive project and it worked fine with an extensive e2e suite
it might be this? https://trpc.io/docs/migrate-from-v10-to-v11#transformers-are-moved-to-links-breakingi found the problem but i don't know how to fix
the version with this problem make my api url like this:
while the correct one is:
yes it looks like superjson's problem
https://github.com/RSS3-Network/Explorer/blob/5567322395d862623bc9baaff2a95a80c2af8e01/src/lib/trpc/provider.tsx#L90
I think I have it configured correctly because there is no typescript error
correct one vs. problematic one
.251 bad
so it's b/w .240 ~ .251
lemme try .248
.248 good
okay it starts from .249
probably to do with the transformers moving but you should have typescript errors to guide you what to do
are you able to locate the commit so that we know what's introduced
it's a bit of a pain b/c it's auto-released on the branch without a git tag etc
omg it has type error
sorry i think the IDE just too lazy to check while i keep updating the deps
cool, yeah this was the one that triggered .249
so it makes sense
https://github.com/trpc/trpc/pull/5414
GitHub
chore(breaking): mv transformer from
createTRPCClient() to links ...Closes #
šÆ Changes
What
Breaking change.
This moves transformers: from createTRPCClient() to links
This will enable us to add support for tupleson without affecting createTRPCClient - it'll ju...
gtg
it actually has a really good type error hint
thank you so much
let me try fix it
it works! thank you Alex!
ā¤ļø