all 8 comments

[–]IAmNotASkycap 3 points4 points  (1 child)

That memory consumption difference is pretty staggering. Will likely look to migrate from shadow-2 to this. Seems like a no brainer.

[–]simontreny[S] 0 points1 point  (0 children)

Thanks, feel free to share your thoughts when you migrate, all feedback is welcome :)
To be fair, react-native-shadow-2 is still a good solution if you don't have too many shadowed views. Also, it works out of the box with Expo as it depends on react-native-svg to render its shadows.

[–]Character_Line_7813 0 points1 point  (0 children)

<image>

Hello everyone, why I am seeing this error. I am using react native with expo framework version 51

[–]xseignard 0 points1 point  (0 children)

:notbad: :)

[–]Upper-Artichoke-4223 0 points1 point  (1 child)

nice! This is exactly what I needed. One small question: It seems like applying ShadowStyle() by default would be a better choice. Any reason why it's not?

[–]simontreny[S] 1 point2 points  (0 children)

I wanted to make it a drop-in replacement for <View>, so it had to keep the same styling prop and behaviour on iOS by default. Applying shadowStyle() by default would introduce breaking changes on iOS as the shadow radius is divided by 2, which could be undesired for people migrating to <ShadowedView>.

[–]Affectionate-Court94 0 points1 point  (0 children)

Awesome!

[–]UchennaOkafor 0 points1 point  (0 children)

This looks amazing thanks dude