Fabrizio Rizzonelli

cuberto’s liquid navigation made with @expo and @swmansion's gesture handler. huge shoutout to @mironcatalin and @kzzzf for the amazing reanimated workshop at @appjsconf

React Native is trending on tech twitter thanks to ⁦@appjsconf⁩ hype 🤩

Having fun with @BelkaDigitalLab’s team @appjsconf from @swmansion Come and say hi if you’re around!

I have 16 personalized reactions on Slack - AMA

@appjsconf @cortinico Congratz @cortinico 😉 Happy that I have the chance to meet you IRL

How #ReactNative evolved in 2022 as a framework and as a community? If you missed any of the React Native releases last year, you definitely don’t want to miss @cortinico's talk! Book your spot for App.js Conf here: appjs.co

@sarafazzini_ Can confirm that

Let me say I know some spots in Verona

@bryla_piotr @BelkaDigitalLab @wcandillon @mironcatalin @Baconbrix Will definitely do! Will I meet you around? :)

@ivolnelly @BelkaDigitalLab @wcandillon @mironcatalin @Baconbrix Awesome 🚀 Enjoy Poland, Fabrizio. Make sure you try Pierogi 🥟 and Żurek 🥣

I'm going to be in Poland with @BelkaDigitalLab's dev team. Looking forward to meet @wcandillon, @mironcatalin, @Baconbrix and all other folks 😎 See you there 🎉

@mazzarolomatteo @reactnative @expo Great thread Matteo! I'm curious, did you try react-native-reanimated out?

Ready to publish this Breathly app update — it's open source so the code will be available soon. Here are a few @reactnative and @expo issues I discovered this week and how I solved them 👇

@anas_araid @pmndrs @bwalkin Wow! That's freaking cool to watch 🚀

iPadOS adaptive cursor built with @pmndrs' react-spring library. inspired by @bwalkin's amazing wwdc talk.

🤌🏿 it's pandoro or go home

obviously made with @expo, @swmansion's gesture handler and a lot of tagliatelle🤌

@sarafazzini_ @mchgli @SlushHQ Subito dopo Pink

@mchgli @SlushHQ @ivolnelly a che ora suonano i Mumford?

In @SlushHQ with @ivolnelly! Let’s check those famous “startups”

@cszhu I swear I've all 5 of 'em 🤌🏿

no software developer has all 5: 1. decent work life balance 2. a love life 3. good mental health 4. ranked gold or higher in league of legends / valorant 5. a m1 MacBook pro

Hey Everyone, We're an indie game team from Italy🍕 We've created this new type of horror extraction game with dark, twisted elements ☠️ If you’re having a good time playing HiO, please consider writing a positive review, thanks❤️ store.steampowered.com/app/964440/Hel… #indiedev #gamedev

@sarafazzini_ @zebriez Most memable person I've ever met

@zebriez can we talk about custom reaction? I’m very proud of my +10 reactions, I added a LinkedIn skill just to mention it. Also, none of these reactions were added by me to the company library.

slack reactions are a deeeeep form of self-expression

@giacomocerquone @mchgli So I think you found out the answer to your problem 🚀

@ivolnelly @mchgli you do that by leaving "expo" (but just expo, not the libs) within the peerdeps pinned to a version! That is how you make sure of that 🙂

Hey there #react #native #expo #experts if you were to build an uploader library for react native and your package would use the expo-document-picker package, would you state this dependency within the "dependencies" field or the peerdeps one? And why? I'm used to the first.

@giacomocerquone @mchgli I've never built a lib plugin based on some expo version tho, so maybe a different use case. I think you somehow need to also keep in mind that every version in expo ecosystem is tied to a SDK release. So the point is how to make clear to the devs which version should they use

@ivolnelly @mchgli also checking at your great SO post (thanks for that 🙏) the libs from the github thread needs to be in dependencies and not in peerdependencies for this last point: "You expect/need the user to work with that other library as well" because no, we actually don't expect that.

@giacomocerquone @mchgli I agree on having them as both devs and peer :)

@ivolnelly @mchgli the smartest choice is probably done by aws amplify which state them as both devdeps and peerdeps github.com/aws-amplify/am…

@giacomocerquone @mchgli I think you can specify the version as peer deps, so breaking changes shouldn't be an issue. The whole point of peer deps is exactly that, to allow devs to manage communication with several packages. I always love this stackoverflow.com/questions/2673… post :)

@ivolnelly @mchgli also if the document-picker is updated, and it's stated as peerdeps, the user should still wait for me otherwise would/could get a crash in case of breaking changes... right?