React: Feature - Best error tracking for React Special Props errors

Created on 16 Feb 2017  路  3Comments  路  Source: facebook/react

I'm currently using React v15.4.1 and this error is displayed in the console:

Warning: li: `key` is not a prop. Trying to access it will result in `undefined` being returned. If you need to access the same value within the child component, you should pass it as a different prop. 

printWarning @ warning.js:36
warning @ warning.js:60
warnAboutAccessingKey @ ReactElement.js:60
dehydrate @ backend.js:7956
dehydrate @ backend.js:7956
(anonymous) @ backend.js:7187
flushBufferSlice @ backend.js:7182
flushBufferWhileIdle @ backend.js:7170

I can't track easily what component trigger this error. I have to do a "binary search" in my code to find it.

Most helpful comment

I updated the extension to 2.0.12 and it works. Thanks @gaearon

All 3 comments

This is not coming from your components. It's an accidental mistake I introduced into React DevTools. Update React DevTools to the latest version, and it'll disappear.

I updated the extension to 2.0.12 and it works. Thanks @gaearon

Sorry for the disruption 馃槉

Was this page helpful?
0 / 5 - 0 ratings