Next.js 13.5 Upgrade: 'Key' Prop Warning Issue

[plain burrow]

I upgraded Next.js to the latest version, 13.5. When I ran the CLI, it displayed a warning message: 'Warning: Each child in a list should have a unique "key" prop.' However, it didn't specify where this issue occurred, and I have many array.map iterations in my project. Could you provide a solution to resolve this?

By the way, I really appreciate the new clean CLI interface ❤️.

[high bone]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[nimble ether]

you must add key in every array.map

The fixes are:

• add the key prop
• disable the eslint rule(will never recommend this)

[plain burrow]

i did it, but i warning me about duplicates key and hard to find it

[nimble ether]

maybe you're rendering same item again and again in same map?

[plain burrow]

I'm not sure, so I'll try removing the array.map calls one by one to pinpoint where the issue is occurring. By the way, will future versions of the Next.js CLI provide more specific information about where this issue occurs?

[nimble ether]

the array.map error is show well in browser

in the console

[plain burrow]

it doesn't show in the browser console but cli. maybe this is server component

[nimble ether]

yeah then that is the reason

[tidal idol]

i also saw a github issue about this; i think this is a nextjs 13.5 bug

https://github.com/vercel/next.js/issues/55642

[sharp spoke]

Usually this would be an warning in console. But if you install eslint it would turned to be a build error. The only way to remove it check and provide where you missed any key prop ( might be in the map function) .This error pops up since you really missed any key props..just find it and provide it.