React-native-windows: Where are the releases for RN 0.43 & 0.44, and RC for 0.45 ?

Created on 23 May 2017  路  8Comments  路  Source: microsoft/react-native-windows

It's been 10 weeks since we had any new releases or release candidates - this project is falling behind facebook react native. What is happening ?

Most helpful comment

Hi James! Activity can be shown in a number of ways, of course :) I've been responding to issues and merging PRs nearly every week for the past 2 months.

The main difficulty was that 43 and 44 were upstream releases that did not work for a lot of people on other platforms, as well as RNW. It has taken us and upstream RN a while to stabilize things so we can responsibly do a release. This is the comment I've put into a few issues over the last weeks. I hope that next time there's questions about the viability of the project that you or your co-workers will ask in the Reactiflux channel or look at the activity feed :)

Hopefully things have turned a corner, but if you're using enzyme or similar popular test tools, they will break with anything based on RN 43 or newer due to upstream packaging of React 16 alpha. Unless there is a feature in 43+ you desperately need, I would advise waiting. Several teams shipping product have extracted new features like flat list into their own component so they can use them in 42.

I'm confident RN 46 will resolve most of these issues across all platforms.

All 8 comments

That is a great outcome, and looking forward to the 0.45 release. Whether it is fair or not, open source projects get judged by how 'active' the project is. I have invested a lot of time and effort in React Native Windows and want to see it succeed. My colleagues were deciding that it has been 'abandoned' based on lack of releases and activity, so you have to ask the question.

Hi James! Activity can be shown in a number of ways, of course :) I've been responding to issues and merging PRs nearly every week for the past 2 months.

The main difficulty was that 43 and 44 were upstream releases that did not work for a lot of people on other platforms, as well as RNW. It has taken us and upstream RN a while to stabilize things so we can responsibly do a release. This is the comment I've put into a few issues over the last weeks. I hope that next time there's questions about the viability of the project that you or your co-workers will ask in the Reactiflux channel or look at the activity feed :)

Hopefully things have turned a corner, but if you're using enzyme or similar popular test tools, they will break with anything based on RN 43 or newer due to upstream packaging of React 16 alpha. Unless there is a feature in 43+ you desperately need, I would advise waiting. Several teams shipping product have extracted new features like flat list into their own component so they can use them in 42.

I'm confident RN 46 will resolve most of these issues across all platforms.

@matthargett Thanks for the update (and for all your work on this!)

@jmcginty There seems to be a serious overhaul of the packager in [email protected] (and potentially 0.45). As a result, *.windows.js files are no longer being picked up correctly. I'm hoping to find a solution to this issue soon. https://www.facebook.com/groups/reactnativeoss/permalink/1683835541913073/

Update: Once this PR - https://github.com/facebook/react-native/pull/14194 - is closed / merged, we should have a working 0.44 release.

thanks for keeping us up do date @rozele , and welcome back :)

Thanks @jmcginty. I'll let the release candidates settle for a few days and then publish final releases, 0.44.0-rc.2 and 0.45.0-rc.0 are out.

Good on you

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dubiao picture dubiao  路  3Comments

JunielKatarn picture JunielKatarn  路  3Comments

rozele picture rozele  路  4Comments

kikisaints picture kikisaints  路  4Comments

syedibrahimt picture syedibrahimt  路  3Comments