[BUG] React warning in Next.JS: React does not recognize the `getClassNames` prop on a DOM element
See original GitHub issueDescription
This is reproducible with either Next.js CodeSandbox:
- Next.js Vanilla JS: https://codesandbox.io/s/chakra-react-select-next-js-dtnsm?file=/pages/index.js
- Next.js TypeScript: https://codesandbox.io/s/chakra-react-select-next-js-typescript-kscuf?file=/pages/index.tsx
But it doesn’t seem to occur in the CodeSandboxes that don’t have Next.js.
This appears to be related to functionality introduced in react-select@5.7.0.
This can be mitigated by pinning react-select to version 5.6.1 or earlier. However, because of the loose requirement versioning, this needs to be done with resolutions
:
"resolutions": {
"react-select": "5.6.1"
}
chakra-react-select Version
4.4.1
Link to Reproduction
- Next.js Vanilla JS: https://codesandbox.io/s/chakra-react-select-next-js-dtnsm?file=/pages/index.js
- Next.js TypeScript: https://codesandbox.io/s/chakra-react-select-next-js-typescript-kscuf?file=/pages/index.tsx
TypeScript?
- Yes I use TypeScript
Steps to reproduce
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Operating System
- macOS
- Windows
- Linux
- iOS/iPadOS
- Android
Additional Information
No response
Issue Analytics
- State:
- Created 10 months ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
React does not recognize the X prop on a DOM element ...
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 `_newProperty` prop ...
I've a “NextJS 11” app. <BuilderComponent model="page" />; is added in my _app file I get this error Message: When I place any...
Read more >Warning: Prop className did not match. #7322 - GitHub
I have deleted the .next folder, closed tab, reopened, and the error stills. react-dom.development.js?ac89:67 Warning: Prop ...
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 >API - React Select
A flexible and beautiful Select Input control for ReactJS with multiselect, autocomplete and ajax support.
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
@csandman yes after update its work! thanks man… you`re the best
I can push a fix for v3 tomorrow!