Jonathan Kolyer

Yeah Please Update NPM. Just bump the version number and push.

I had to fork the repo to insert ESLint, which is a big PITA. The rules are not easily converted.

Yes I just narrowed it down to some change between react-native-screens alpha.12 and alpha.22. @jrwpatterson what about `usescreens` is the problem? do you have a workaround?

The problem is introduced in react-native-screens `1.0.0-alpha.18`. alpha-17 works OK.

@chrfalch [This change causes the blocker on Android](https://github.com/kmagiera/react-native-screens/pull/50/commits/639cf77ea1fc76dbceddddb22f834c3f06e26fce#diff-431504e69caf4f9d42d9aeb0f9ddc19a).

@chrfalch [Possibly](https://github.com/kmagiera/react-native-screens/issues/61)

yes On Sun, Nov 6, 2022 at 10:17 AM Benz19 ***@***.***> wrote: > HI @jkolyer Im going through all the open > issues trying to help get things cleaned up...

Doc is fairly minimal and doesn't give transparency into how to setup the hierarchical crew. It would help to understand better when to use sequential and not. Some use cases...

Got the same cryptic error from the `p-map` npm package. Don't know any workaround other than don't use it.

> They are built-in modules/objects. If you're using node.js. But not if you're running the code in react-native or in browser. Nowhere is this dependency made explicit.