Unknown props with React 15.2
See original GitHub issuereact-select now throws a warning when using React 15.2:
warning.js:44 Warning: Unknown prop `minWidth` on <input> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
in input (created by AutosizeInput)
in div (created by AutosizeInput)
in AutosizeInput (created by Select)
in div (created by Select)
in div (created by Select)
in Select (created by Async)
in Async (created by ComposePage)
in div (created by ComposePage)
in div (created by ComposePage)
in div (created by ComposePage)
in div (created by ComposePage)
in ComposePage (created by RouterContext)
The React team says this needs to be fixed as it will break in the next major release: https://github.com/facebook/react/issues/7152#issuecomment-230273479
Issue Analytics
- State:
- Created 7 years ago
- Reactions:24
- Comments:7 (1 by maintainers)
Top Results From Across the Web
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 >дэн on Twitter: "How to fix React 15.2.0 “unknown DOM property ...
It won't be removed, the problem is when you pass arbitrary props to DOM components.
Read more >react-redux connect pattern to avoid unknown props warning ...
I just solved the same issue. The dispatch prop is there because you are not providing mapDispatchToProps when you call connect() .
Read more >i18n-react - npm
React 15.2 is preparing to stop filtering HTML properties (https://fb.me/react-unknown-prop) - the feature that i18n relied upon for ...
Read more >react-valid-props 1.0.12 vulnerabilities | Snyk
A little helper to get around unknown property in react 15.2 · latest version · latest non vulnerable version · first published ·...
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
I’ve fixed this upstream and updated react-input-autosize, which should fix this. Will get a new npm release of react-select published as soon as I’ve completed testing & changelog for the fixes since the last release.
I moved to
react-selectize
(not to critizereact-select
, which is great, but this fixed my immediate problem)