`npx create-react-native-dapp` errors out
See original GitHub issue-
I’m submitting a … [x] bug report [ ] feature request [ ] question about the decisions made in the repository [ ] question about how to use this project
-
Summary
npx create-react-native-dapp
errors out:
[21:20:44] Error: Problems validating fields in app.json. See https://docs.expo.io/versions/v40.0.0/workflow/configuration/
[21:20:44] • is missing required property 'name'.
[21:20:44] • is missing required property 'slug'.
Warning! Your git working tree is dirty.
It's recommended to commit all your changes before proceeding,
so you can revert the changes made by this command if necessary.
[21:20:44] Input is required, but Expo CLI is in non-interactive mode.
Please specify eject method (bare, expokit) with the --eject-method option.
(node:9459) UnhandledPromiseRejectionWarning: Error: Command failed: cd /Users/foobar/.../my-react-dapp; expo eject --non-interactive;
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at ejectExpoProject (/Users/collinglass/.npm/_npx/9459/lib/node_modules/create-react-native-dapp/build/main/buidler/index.js:61:21)
at Object.create (/Users/collinglass/.npm/_npx/9459/lib/node_modules/create-react-native-dapp/build/main/buidler/index.js:720:5)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async /Users/foobar/.npm/_npx/9459/lib/node_modules/create-react-native-dapp/build/main/cli/index.js:115:33
(node:9459) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:9459) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
111
- Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
Using nvm on mac, tried with node v12.20.0 and v13.12.0, same error.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Apple Silicon (M1) Error to create React Native app #34449
1 - Create an empty project. npx react-native init AwesomeProjectExample · 2 - Move to the project folder. cd AwesomeProjectExample · 3 -...
Read more >Troubleshooting - React Native
These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here, ......
Read more >I can't install react using npx create-react-app? - Stack Overflow
This happens is if one of the node modules requires to install your react app is missing. The other reason is if your...
Read more >Addressing common errors in React Native - LogRocket Blog
Explore common React Native errors such as "command not found" and learn about their causes and potential solutions.
Read more >Create a New React App
If you're learning React or creating a new single-page app, use Create React App. If you're building a server-rendered website with Node.js, try...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes I am, just reverified that
@collinglass Great to hear you found a solution! Best of luck.