Max
Max
Hey @jthegedus, thanks for opening this, I was just about to! #### To contextualise this issue: I think that from the perspective of a new user, encountering this error is...
> Found this Github issue when encountering the same exact problem. In my case, the node versions are different (14.15.4 and 14.17.0), but the same problem where the shim-versions for...
You're absolutely right. This would work in the vast majority of cases. It is definitely kind of crazy to spin up an entire JavaScript virtual machine just to pass on...
Is there any appetite to make this path less brittle? One idea would be to expect `gradlew` to be at `../../gradlew`. This would make it look for `gradlew` next to...
After thinking about this a bit more, I don't think that's necessary; I think that just replaces one brittle path with another. I think the best way to handle this...
~I'm also experiencing this on a non-expo project with~ ```json "react": "18.2.0", "react-native": "^0.72.4", "react-native-gesture-handler": "^2.12.1", "react-native-reanimated": "3.4.1", "react-native-reanimated-carousel": "4.0.0-alpha.9", ``` ~After some trial and error, I determined that using...
I just tried to reproduce the issue again with the above dependencies on my machine and again on another machine and I can't. It looks like `"react-native-reanimated-carousel": "4.0.0-alpha.9",` does indeed...