React-select: minWidth on <input> tag is invalid

Created on 2 Jul 2016  路  29Comments  路  Source: JedWatson/react-select

Hi,

There is a breaking change in your ReactInputAutosize library in React 15.2.0 that reports the above error.

For now, I have just downgraded back to 15.1, but this may be something you wish to fix (correcting it in react-input-autosize and bumping the version in this one).

To repro, just upgrade react and view a Select.

Most helpful comment

Just released to npm. Hopefully the last of the beta releases too. Y'all are lucky, I skipped watching a movie on my sunday evening to get this all tested and released 馃槃

All 29 comments

Facbook developer explaining this warning: https://fb.me/react-unknown-prop

@mattgi can you explain the broken behavior? I'm seeing the warning, but not any problems with the component.

@JedWatson can you please push npm version with this fix?

+1 for the npm push! :)

+1. Please merge this. I get Unknown propminWidthon <input> warning, and it isn't a short warning. Quite a lengthy one. Very annoying.

+1. Please merge this :)

+1. Mission critical =)

+1

+1

Just released to npm. Hopefully the last of the beta releases too. Y'all are lucky, I skipped watching a movie on my sunday evening to get this all tested and released 馃槃

@JedWatson Thank you!

Dedication!

Thank you, much appreciated!

I installed the 1.0.0-beta14 version but I still see the warning. What is wrong? thanks

Are you sure its actually 1.0.0-beta14. You can check that with npm ls --depth=0.
I suspect in your package.json you declare ^1.0.0-beta14. But since npm thinks 'beta9' is higher than 'beta14' (alphabetical order) it installs the wrong version. So you need to declare 1.0.0-beta14 (no ^) in package.json.

I can confirm the issue is fixed @ayozebarrera

great @katgironpe. I think my problem is about @wirmar said... beta9 higher than beta14 on npm.

thanks!

Can someone push bower version of the fix? it's still not fixed on bower :(

Thanks! 1.0.0-beta14 -fixed.

This seems to be back in the rc1 release.

+1

I can confirm - its back in 1.0.0-rc.2

Any updates on this? Appears it was a minor fix, but for some reason was then reverted in rc1 and rc2.

+1

What has happened with this?

+1

Could it be possible to release a 0.9.2 with this fix? 馃檭

Issue still persists for me on 0.9.1. Component works as expected, with this annoying error.

Need this. latest version of react and react-select with bower.

Was this page helpful?
0 / 5 - 0 ratings