React 17 Support #1152
Comments
|
Yeah I was about to start a project with React and Evergreen. Step 1 install react. Step 2 install evergreen Step 3 .......oh...step 2 failed |
|
When will this get updated? Such a great package and would love to use it with latest version of React |
|
Hey y'all -- will look into this before the week's done. My guess is it's as simple as loosening up the peer deps requirement (or getting rid of it altogether) to allow for React 17 (especially since there aren't really any major breaking changes in React 17), but I want to be 100% sure first and test locally. Thanks for the patience here 🤞 |
|
Any updates on this? |
|
This should hopefully be a small update as you say - as there's no breaking changes between React 16 and 17. next.js users can't upgrade to next 11 until Evergreen supports React 17 so it would be timely if the dependencies were updated. |
|
Any updates.....? |
|
Thumbs up for React 17 please! |
|
Hey folks, quick update – we've made some upgrades internally and with packages that would have led to a breakage on React 17 (this only affects certain components). Right now it seems the last package that we'll need to fork or switch off of is I started looking into switching to react-window which seems to be the defacto standard these days, but it's noticeably slower than react-tiny-virtual-list (this will affect SelectMenu, Table.VirtualBody, and Autocomplete components). |
|
Ok, gonna cut a release soon now that these have landed: |
|
Released with v6.3.0! |
|
@mshwery - many thanks for your work! |
Are there any plans to bump the react and react-dom peer dependencies to allow react 17? With the npm version 7 reintroduction of installing peer dependencies it is making it tricky to use evergreen without the
--legacy-peer-depsflag.The text was updated successfully, but these errors were encountered: