React Native todo app get stuck on npm and crashes when built on Mac

[kshehata]

React Native todo app get stuck on npm and crashes when built on Mac

[MongoCaleb]

@kshehata thanks for reporting this! I am seeing the same thing on my M1, while other configurations are working just fine. We're investigating.

[kshehata]

Ok, let me know if there's anything I can do on this end to help debug.

[kshehata]

I started with the React Native starter app and then brought things over and now I have something that at least runs in the simulator. Not sure why this works and the repo here doesn't.

https://github.com/kshehata/TodoApp

[krollins-mdb]

@kshehata, can you share the following info?

• Node.js version
• In the failing project, run npm install -d verbose realm and copy-paste the results here

This is potentially a problem with Node.js and Realm.js version compatibility. If so, I'd like to let the engineering team know or at least add warnings to the tutorial.

Realm.js had a known issue with Node.js v19, but that should have been addressed a long time ago. v11.5.2 had a fix for it.

[krollins-mdb]

@MongoCaleb, you were on Node.js v20.something, right?

[kshehata]

node --version tells me v20.3.0

I switched to yarn as npm would just stall on reifying. If I run npm with those options I get:

npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "from" argument must be of type string. Received undefined

[kshehata]

Not sure if this helps, here's what happens if I run yarn:

(base) user@machine react-native.todo.flex % yarn add -d verbose realm
yarn add v1.22.19
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " > @realm/[email protected]" has incorrect peer dependency "realm@^11.0.0-rc || ^11.0.0".
warning "@realm/react > [email protected]" has incorrect peer dependency "[email protected]".
warning "@realm/react > react-native > @react-native/[email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning "@realm/react > react-native > @react-native/codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning "react-native > react-native-codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning " > @react-native-community/[email protected]" has unmet peer dependency "prettier@>=2".
warning "@react-native-community/eslint-config > [email protected]" has unmet peer dependency "prettier@>=2.0.0".
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
success Saved 4 new dependencies.
info Direct dependencies
└─ [email protected]
info All dependencies
├─ [email protected]
├─ [email protected]
├─ [email protected]
└─ [email protected]
✨  Done in 8.60s.

[krollins-mdb]

I can replicate when using Node.js v20.3.0. I'll make sure the engineering team is aware and see if we can come up with a workaround while they're looking into a fix.

[krollins-mdb]

@kshehata, could you try using an older Node.js version (v18.16.0 works for me) to help determine whether the issue is compatibility with Node.js v20.3.0?

[krollins-mdb]

@kshehata, seems like the problem was something in the project's package-lock.json file. If you delete that and then npm install, it should work.

I have a PR up to address this with the template app itself.

Thanks for filing this issue!

[krollins-mdb]

I can install the template app locally now when using Node.js v20.3.0. Closing this issue. Let me know if you still experience problems.