Tomasz Żelawski

Hi @gkasireddy202. The recommended way of installing the pods in React Native currently is `bundle install && bundle exec pod install`. Please check if it fixes your issue.

This seems like outdated `@babel/preset-typescript` potentially. Try to upgrade it (regenerating yarn.lock should do the trick).

@DanielKuhn I looked into your package.json and yarn.lock, created new RN App using 0.73.6, copied your package.json and yarn.lock there, removed all irrelevant dependencies and everything worked fine. From what...

It's the standard for React Native to take the code from the source for bundling, all libraries point `react-native` target to source code. I don't know why however, I admit...

Hi @gaearon, just to be curious - does this happen when you attach the same handler to multiple components? If yes, then [my comment](https://github.com/software-mansion/react-native-reanimated/issues/5345#issuecomment-1859198802) applies here as well.

@gaearon I messaged you in Discord because I have some trouble building Bluesky to test it.

Hi, I'm currently investigating this issue. I will keep you updated as soon as I learn about the causes. I can already give a few answers here: - `scrollEventThrottle` property...

As you may noticed I opened an issue about this on `react-native` GitHub since I narrowed it down to be stemming only from `react-native` - after I rewrote your repro...

Sorry for the late reply about that but in regard to event names, yes, it's correct. We are adding a timestamp on the beginning of event name since this [PR](https://github.com/software-mansion/react-native-reanimated/commit/535b5d64c0720da3a9a39d99a67e878fe09b5154)...

@efstathiosntonas I think it's more about layout and non-layout prop, `transform` is a non-layout props, meaning, changing component's `transform` property does not affect other components layout (position), they do not...