React does not recognize the `motionProps` prop on a DOM element.
See original GitHub issueDescription
Problem occurred every time I open the drawer.
Link to Reproduction
https://codesandbox.io/s/black-leftpad-f5lo5b?file=/src/App.js
Steps to reproduce
No response
Chakra UI Version
2.3.4
Browser
Microsoft Edge
Operating System
- macOS
- Windows
- Linux
Additional Information
Warning: React does not recognize the motionProps prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase motionprops instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Issue Analytics
- State:
- Created a year ago
- Reactions:12
- Comments:22 (1 by maintainers)
Top Results From Across the Web
React does not recognize the X prop on a DOM element ...
[Error] Warning: React does not recognize the providerId prop on a DOM element. If you intentionally want it to appear in the DOM...
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 >Warning: React does not recognize the `isOpen` prop on a DOM
prop on a DOM element. i got solved this issue. just change tag to Navlink because ActiveClassName is just suported Navlink.
Read more >Unknown Prop with Framer Motion and React : r/webdev
React does not recognize the `layoutId` prop on a DOM element. If you intentionally want it to appear in the DOM as a...
Read more >React does not recognize the `HOGE`が出た時の対処法 - Zenn
Warning: React does not recognize the `drawerWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as...
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 FreeTop 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
Top GitHub Comments
Good catch, @martinezleoml. The issue was that the transition package was not released properly. That’s my bad.
I’ve now added it to the next release. It should work as expected afterward
I updated to
@chakra-ui/react@2.3.6
and the error is gone. Thank you guys!