TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Who's tired of upgrading React Native?

30 pointsby jconleyabout 3 years ago
It seems to always take my team and I a day or more to do a React Native upgrade. So much lost time. Anyone else have this issue? Any horror stories? It once took us a full two weeks with some breaking changes in libraries for an OS version update.

8 comments

steve_adams_86about 3 years ago
The last time I worked on a react native project my team and I wondered all the time if we were doing something seriously wrong or not.<p>It seemed like very popular and commonly used dependencies had poor community support. Upgrades were often painful. Breakage during routine package upgrades occurred far more than in our non-RN typescript projects.<p>We did a lot of research and asked around but it seemed to be par for the course.<p>Overall I’d guess that we still saved time over learning and developing with native solutions for iOS and android, but it left me feeling like the ecosystem could be so much more productive still.<p>I’ll admit I recognized the need to contribute to libraries I saw were lacking support, but the project wasn’t my main focus and I don’t think my employer cared much. In the future I should definitely complain less and help more.
评论 #31200269 未加载
March_f6about 3 years ago
100%. No particular horror stories just tons of time lost and frustrating dependency issues. Studying Swift now to go native.
评论 #31201719 未加载
jrvarela56about 3 years ago
Not at all. I use Expo tho :P <a href="https:&#x2F;&#x2F;expo.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;expo.dev&#x2F;</a>
评论 #31200194 未加载
评论 #31197021 未加载
skydhashabout 3 years ago
I had to do this recently. I just create a new project, and move the deps and js code files in it. And then fix whatever is breaking. The great thing is that they didn&#x27;t have a lot of stuff done native side. The biggest changes was updating react-navigation to 5 from 3
评论 #31197903 未加载
评论 #31203236 未加载
handsome_latinoabout 3 years ago
I second many users here as to the caveats of React Native. I check and try new projects from time to time, and support does get a bit better especially with Expo.<p>For me (as a Software Engineer focused on UX) it was how &#x27;unnatural&#x27; apps created looked on either iOS or Android without having to do a lot of tweaking or work. I&#x27;m unfortunately not a big fan of Java (personal reasons but mostly coding style preference), so still have a bit of faith on React Native (React being one of my faves and most used frameworks).
atonseabout 3 years ago
What’s the solution here?<p>seems like something more centralized like deno which has a big set of standard libs with stability guarantees?<p>Cuz I have avoided upgrading nativebase for 3 years now.<p>Our react native codebase is pretty small but still a pain to build.
serdabout 3 years ago
I upgraded from 0.64.2 to 0.67.4 recently. It was much easier than I expected. Looking at the logs, I had to use &quot;react-native-clean-project&quot; for some reason.
swahabout 3 years ago
Yes - I try to... not upgrade when possible.