Vyacheslav Goreev comments

Results 6 comments of


                                            Vyacheslav Goreev

mini-css-extract-plugin throws "Conflicting order" errors during build

I had the same problem. The solution was to **rearrange imports** in the top of the component or page that caused this kind of warning. I moved the **import of...

ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use the ref instead. This method will be removed in a future release.

@Preeternal please, see this response. Reanimated should be of v1. `yarn add react-native-reanimated@1` https://github.com/computerjazz/react-native-draggable-flatlist/issues/244#issuecomment-777841894

ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use the ref instead. This method will be removed in a future release.

> Hello, I have the same and my project works with expo, I tried the different methods but I had errors 500. and so I came back to version 2...

ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use the ref instead. This method will be removed in a future release.

Exactly the same fix were added to the library in https://github.com/computerjazz/react-native-draggable-flatlist/pull/278/files

ReactNativeFiberHostComponent: Calling getNode() on the ref of an Animated component is no longer necessary. You can now directly use the ref instead. This method will be removed in a future release.

> How do I go about it? > i begining to react-native, can you give me directive for solve problems. 1. Use reanimated v2 2. Add the code I provided...

`manypkg check` shouldn't warn to mirror `peerDependencies` into `devDependencies` when they're already available in the root's `dependencies`.

@threepointone this feature will be highly appreciated!