jlarmst
v11 `Invalid Content-Type header`
The most recent update of v11 seems to break with:
The related commits in the rc.346 are probably:
- https://github.com/trpc/trpc/pull/5613
- https://github.com/trpc/trpc/pull/5652
I am using the react and vanilla fetch adapters, so according to the docs https://trpc.io/docs/migrate-from-v10-to-v11#explicit-content-type-checks-non-breaking my code should not be breaking
I went ahead and downgraded to
11.0.0-next-beta.318
and it works fine15 replies
SSR with initialData throws error
I'm using SSR with Astro and have a client that looks like
It works fine if I create a
But, trying to use SSR with the component and passing the initialData received from the vanilla client throws an error Also, I'm using v11 Also, I know that the initialData is not undefined because I'm rendering it to the screen with Astro
client:only
react component or if I fetch the data with the vanilla client in Astro.But, trying to use SSR with the component and passing the initialData received from the vanilla client throws an error Also, I'm using v11 Also, I know that the initialData is not undefined because I'm rendering it to the screen with Astro
9 replies