Mateusz Łopaciński

> We can’t support anything we’re not testing, and this doesn’t add v9 to tests. I know, that's why this PR is still a draft. I just started working on...

@ljharb I fixed most of failing tests and adjusted them to eslint v9 style. There are 5 remaining rules which tests still don't pass. I can get back to fixing...

> Don't worry about the linting yet; the import plugin has to come first for that. > > However, we already have to retain compatibility for every eslint version we...

@Martinocom-Switcho One little clarification here. The fix shipped in `3.17.5` that you mentioned was not related to layout animation freezes/crashes. It just fixed style inconsistence for worklet-based animations (these created...

@igorkos `3.18.0` had a regression that introduced this `exiting` animations issue on the Old Architecture. You'd have to bump reanimated to `3.19.0` for the issue to be fixed (and also...

Hey @hannojg! Thanks for your proposal. I appreciate your effort and all the suggestions you made. Although your suggested changes look promising, I feel that they make the current already...

One more thing here. I know that using layout transitions with animated styles is hacky and is not something that we officially recommend or support but behavior is also different...

> I see that latest stable reanimated version does not yet support RN 0.79. Latest reanimated version (`3.18.0`) supports RN from `0.75` to `0.80`, so `0.79` is supported as well....

> it's my misunderstanding, reading the release notes the only explicit mention of support to 0.79 was version 4.x beta; but then 3.18 mention supporting 0.80 so it's on me....

Reanimated `3.6.0` is not compatible with RN `0.74.x`. Please take a look at the compatibility table [here](https://docs.swmansion.com/react-native-reanimated/docs/guides/compatibility/) and bump reanimated to the compatible version. The minimum compatible version for both,...