Open AmazingTurtle opened 1 year ago
Im on next 13.5.3
and next-superjson-plugin 0.5.9
, bug is still alive.
For me it's happening even with just 1 child. Notice, that ProductDetails
is a server component, while ProductProvider
(ofc) is not.
<ProductProvider value={state} data-superjson>
<ProductDetails />
</ProductProvider>
observed on next@14.1.1-canary.49
, next-superjson-plugin@0.6.2
A workaround that worked for me at the moment is wrapping the values passed in a "wrapper" using the class-transformer
.
import { instanceToPlain } from 'class-transformer';
export function superjsonWrapper<T extends object>(obj: T): T {
return instanceToPlain(obj) as T;
}
That seems to work for me!
experience the exact same issue as described and have no idea how to fix it. For now, I don't use the plugin and simply ignore the warnings about dates passed around between server and client components. 🤷🏻
The solution proposed by @AmazingTurtle sadly didn't work for me.
Verify Next.js canary release
Describe the bug
I see the
Each child in a list should have a unique "key" prop.
warning message on the client side on multiple occassions, basically every I figured out, that is, because I'm feeding the data to the react context api.Which components are affected? Apparently the warning appears for every node where there are more than 1 children. That goes for normal components as well as plain jsx.
A full error log:
I am using the
13.2.4-canary.8
version of next.Expected behavior
I expect to see no warning about missing unique key props
Reproduction link
No response
Version
0.5.6
Config
Additional context
File
document-list-context.tsx
File
page.tsx