Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unknown prop `_radiumDidResolveStyles` on <div>
See original GitHub issueIm getting this error in console and menu don`t show up. How to solve?
Warning: Unknown prop _radiumDidResolveStyles on <div> tag. Remove this prop from the element. For details,
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Remove unknown props on <div> tag · Issue #759 - GitHub
The style-root component is receiving all props passed to it. We should remove unused props as future versions of React React v15.2.0 will ......
Read more >Unknown Prop Warning - React
The unknown-prop warning will fire if you attempt to render a DOM element with a prop that is not recognized by React as...
Read more >React - Unknown prop `page_id` on <div> tag. Remove this ...
... I got this error from React: Warning: Unknown prop page_id on <div> tag. Remove this prop from the element. For details, see...
Read more >unknown prop warning, styled-components unknown prop, react ...
The unknown-prop warning will fire if you attempt to render a DOM element with a prop that ... Warning: Unknown prop `_radiumDidResolveStyles` on...
Read more >Get rid of `Unknown props` react's warnings : HUB-4674
When opening dashboards list: Unknown props selectedLabel , description , originalModel ... Widgets list Unknown prop applicationName on <div> tag.
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
This is caused by upgrading to React 15.2, which introduces warnings about unknown props.
The actual error is being thrown by Radium, which this package depends on. Looks like they already have an issue open about this: https://github.com/FormidableLabs/radium/issues/759
So you can keep an eye on that for updates, or downgrade to React 15.1 to avoid the error for now if it’s an issue.
This is fixed in v1.9.9.
Thanks for the link to the more thorough explanation @SpainTrain. I did not know about the left-most non-zero digit rule when using caret ranges. I’d read https://docs.npmjs.com/getting-started/semantic-versioning#semver-for-publishers, and other things which unfortunately all failed to specifically mention this detail.
Yay for learning new things at least 😄