-
Notifications
You must be signed in to change notification settings - Fork 1.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
Add react-native upgrade-windows command #674
Comments
Any progress/plan on this? The recent change in how Yoga is referenced was a good example why this can come handy (as opposed to manually mucking with templates and figuring out what/how has changed in csproj/sln templates) |
@achipa Thanks for pinging on this. I think the right solution is to build the right, stable project configuration hooks into react-native-windows so we don't have to deal with breaking changes. One such attempt was recently added in the 0.55 RC: The problem comes along with what projects need to be added to the |
So, I think I've just convinced myself we need to bump the priority on this so we can easily support building from source :-) |
Not sure if this is a dupe or just related to #1358 |
Related (two different implementation points for the same issue), in the sense that it's a separate project for upgrading the templates via git, whereas this issue describes it as part of react-native-windows. I can think of arguments for both, so can't really say I have a preference (as long as there is a way to track these upgrades in at least a semi-automated fashion). |
We are not investing in new features or lower priority bug fixes on vCurrent. The bulk of investment is now in vNext as we prepare to make that the default choice. If this issue is still relevant on the vNext implementation please open a vNext issue. If this issue is of significant severity for a vCurrent app and vNext is not an option, re-open with justification. |
We're going to need something to re-run the yeoman generator (like react-native upgrade).
The text was updated successfully, but these errors were encountered: