-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releasing v5 [TypeScript] Umbrella #4559
Comments
Any chance of publishing a beta build to NPM? 🙂 |
Everyone, please note that this major release will be a complete rewrite so we officially halted PR's until release so we can focus on addressing on breaking changes and documentation. It is absolutely inexcusable that so many PR's have not been addressed but also know that quite a bit focus around Menu positioning, scrolling and sizing behavior are being looked at holistically and may be resolved in batch as we continue to experiment with Popper as a solution. |
We've released a beta. Give it a try and let us know if you run into any issues. |
This new update looks great (especially the TypeScript support). However dropping IE11 support unfortunately makes it a non-starter for us. I was wondering whether that decision could be reconsidered. I see that the main reason for dropping IE11 support seems to be lack of support for CSS grid, but IE11 does partially support CSS grid so I am wondering if it would be possible to get the auto-sizing grid hack to work with it. @ebonow Did you attempt to get the grid hack to work with IE11? Is there a specific reason why it won't work? |
Is there a reason you got rid of I found them useful for those who has a lot of custom logic or customization and wants to keep it in one component without copy-pasting, but still wants to separate Async and Common to different components for export and provide ability to have non-async and async select that had been customized in one place. I might assume it would be handful to have it in v5 too. If it is not a thing for v5, how you would recommend to fix this issue? (Sorry if it is a noob question as I am a bit lost without docs) Should we use not a default export |
@nicoburns
|
I think the world has to let IE die. |
5.0.0 has been released! |
What needs to be done to update the documentation at https://www.npmjs.com/package/react-select ? It still references the old v2 to v3 upgrade guide, etc. 🙂 |
Hello @Bosch-Eli-Black, thanks for bringing this discrepancy to our attention. Seems like the packages |
@Rall3n Np! 🙂 |
As originally discussed in #4142 we've rewritten react-select in TypeScript (🙌 huge props to @Methuselah96 for the heavy lifting here!)
This issue is to track the work involved in merging the TypeScript conversion (#4489), and getting a new major version (v5) released.
Steps
__isNew__
handlingreact-autosize-input
@ebonow PR Remove AutoSizeInput #4625The text was updated successfully, but these errors were encountered: