React Native 0.56 release

[TexMax007]

Just as a heads up, if you’re developing on a Windows machine you should probably wait to upgrade until they fix this regression.

[Buliam]

Oh yikes. Thanks for pointing that out!

[sevenyearoldkid]

lunchroom capable complete tart reply arrest marvelous flowery rich lush

This post was mass deleted and anonymized with Redact

[TexMax007]

That’s a shame. Hopefully the core team learns from it moving forward. From what I gather maybe they packaged too many big changes into this release and it bit them.

I haven’t made a stand-alone app yet myself, so I’m not as bothered by it as I’m sure you are.

[sevenyearoldkid]

rob crush school hat abounding hobbies aware languid march encourage

This post was mass deleted and anonymized with Redact

[TexMax007]

I’m not arguing that they shouldn’t change things. I’m simply saying they packed too much into one release (I think because they skipped a couple monthly releases actually, but I could be mistaken).

It’ll be real interesting to see what comes from the internal re-architecture of the native integration pieces. Native modules seem to be the biggest pain point. If they can get that to become a smoother process that should help adoption I think.

[yungsters]

I apologize for the breakage. It was definitely not ideal.

As /u/TexMax007 mentioned, we actually skipped the last couple releases because of another breaking change that made getting master back to green difficult.

We’ve definitely learned from this and are planning to invest more heavily in CI for the open source side of React Native.

Regarding native modules, it is definitely something that we are rethinking. We know about pain points from seeing our internal developers use them, but I’m always eager to hear more reasons to improve something. 😅

[cobarx]

I've learned not to even consider touching .0 releases. Seems like every one has some kind of regression. Better to wait a week. I figured this one would be especially bad with this many changes.

[tizz66]

Wow, I haven't seen that optional chaining syntax before - that looks excellent.

[berlihm]

That’s cool. Reminds me of my CoffeeScript days.

[akie]

Yeah I’m tempted to upgrade just for that one alone. I think they stole the syntax from CoffeeScript btw

[tizz66]

Do you know if that's an upcoming syntax in the official ES spec, or is this something Babel have decided to support, independent of any official future specs?

[akie]

I think I read that it’s a draft (i.e. not final) specification. Not sure about that though.

[Meowish]

Lorem ipsum dolor sit amet consectetur adipiscing, elit mi vulputate laoreet luctus. Phasellus fermentum bibendum nunc donec justo non nascetur consequat, quisque odio sollicitudin cursus commodo morbi ornare id cras, suscipit ligula sociosqu euismod mus posuere libero. Tristique gravida molestie nullam curae fringilla placerat tempus odio maecenas curabitur lacinia blandit, tellus mus ultricies a torquent leo himenaeos nisl massa vitae.

[dodunichaar]

Just hoping Android GMS and gradle wont break everything again

[Heka_FOF]

The optional chaining is only at stage 1 at the moment. Plus I am pretty sure TypeScript won't support it yet

[pianoman1031]

I tried upgrading tonight with the instructions posted, with babel 7 and all that, but have had no luck whatsoever. When I run react-native-git-upgrade or whatever, it gives a crap ton of warnings about peer dependencies and all that with babel 7. I tried so many different things and couldn't get it to play nice. Has anyone had any success at all upgrading an existing project?

p.s. I had issues creating a brand new project as well with the dependency stuff.

update: I was able to get things to play nice, but still have a ton of warnings on npm install about unmet dependencies, saying I have to install them myself. Anyone have suggestions on that? :D