[gatsby-starter-blog-theme] Clean up react keys warning
See original GitHub issueA new project instantiated using gatsby-starter-blog-theme
currently displays the following error:
Warning: Each child in a list should have a unique "key" prop.
Check the top-level render call using <body>. See https://fb.me/react-warning-keys for more information.
in EmotionCssPropInternal
Need to investigate and clean this up
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Getting key prop warning in React, even though key is set
I'm getting this warning: Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of...
Read more >Lists and Keys - React
When you run this code, you'll be given a warning that a key should be provided for list items. ... Most often you...
Read more >Warning: Each Child in a List Should Have a Unique 'key' Prop
If the key is an index, reordering an item in the array changes it. Then React will get confused and re-render the incorrect...
Read more >Everything you need to know about the key prop in React
NOTE: effect cleanup actually happens after the new component has been mounted, but before the next effect callback is run. For class components ......
Read more >8 common React error messages and how to address them
However, it's also common to receive a React warning in your browser's console saying that every child in a list should have a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You have to ensure the script tags have a key prop as well. So do something like this:
<script key="my-script" src="https://gatsby.dev/my-script" />
Hey, on v0.2.23 I’m getting a similar error
Do you think this is still theme-ui related? (referenced issue above #55)