Clean create-react-native-app not starting - react-native

A clean create-react-native-app AwesomeProject is not starting.
Probably something on my environment not properly configured. I messed around with node and npm but I'm not familiar with them so I might have messed something up.
npm -v 6.0.1
node --version v9.4.0
create-react-native-app version: 1.0.0
0 info it worked if it ends with ok
1 verbose cli [ '/home/caiof/.nvm/versions/node/v9.4.0/bin/node',
1 verbose cli '/home/caiof/.nvm/versions/node/v9.4.0/bin/npm',
1 verbose cli 'start' ]
2 info using npm#6.0.1
3 info using node#v9.4.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle AwesomeProject#0.1.0~prestart: AwesomeProject#0.1.0
6 info lifecycle AwesomeProject#0.1.0~start: AwesomeProject#0.1.0
7 verbose lifecycle AwesomeProject#0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle AwesomeProject#0.1.0~start: PATH: /home/caiof/.nvm/versions/node/v9.4.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/caiof/dev/react/react-native/native-apps/AwesomeProject/node_modules/.bin:/home/caiof/.nvm/versions/node/v9.4.0/bin:/home/caiof/dev/bitcoin-core/bitcoin-0.15.1/bin:/home/caiof/dev/android-sdk/platform-tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle AwesomeProject#0.1.0~start: CWD: /home/caiof/dev/react/react-native/native-apps/AwesomeProject
10 silly lifecycle AwesomeProject#0.1.0~start: Args: [ '-c', 'react-native-scripts start' ]
11 silly lifecycle AwesomeProject#0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle AwesomeProject#0.1.0~start: Failed to exec start script
13 verbose stack Error: AwesomeProject#0.1.0 start: `react-native-scripts start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/home/caiof/.nvm/versions/node/v9.4.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:283:16)
13 verbose stack at EventEmitter.emit (events.js:160:13)
13 verbose stack at ChildProcess.<anonymous> (/home/caiof/.nvm/versions/node/v9.4.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:160:13)
13 verbose stack at maybeClose (internal/child_process.js:943:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid AwesomeProject#0.1.0
15 verbose cwd /home/caiof/dev/react/react-native/native-apps/AwesomeProject
16 verbose Linux 4.15.0-20-generic
17 verbose argv "/home/caiof/.nvm/versions/node/v9.4.0/bin/node" "/home/caiof/.nvm/versions/node/v9.4.0/bin/npm" "start"
18 verbose node v9.4.0
19 verbose npm v6.0.1
20 error code ELIFECYCLE
21 error errno 1
22 error AwesomeProject#0.1.0 start: `react-native-scripts start`
22 error Exit status 1
23 error Failed at the AwesomeProject#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Related

How can I solve [error] No files matching the pattern were found: npx prettier --write $(git diff HEAD origin/master --name-only)

I have set up for ionic 5 application.
Installed prettier as global and even added all the eslint and prettier dependencies
run npm install
configured my package.json script to run eslint-fix
After while trying to run npx prettier --write $(git diff origin/master --name-only)
getting below error,
shows the error reporting No files matching the pattern were found
NPM log as below
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'lint-fix' ]
2 info using npm#6.14.11
3 info using node#v14.15.5
4 verbose run-script [ 'prelint-fix', 'lint-fix', 'postlint-fix' ]
5 info lifecycle AvPlat#0.0.1~prelint-fix: AvPlat#0.0.1
6 info lifecycle AvPlat#0.0.1~lint-fix: AvPlat#0.0.1
7 verbose lifecycle AvPlat#0.0.1~lint-fix: unsafe-perm in lifecycle true
8 verbose lifecycle AvPlat#0.0.1~lint-fix: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/avplat/Roshan/AvplatV3/avplat-v3/node_modules/.bin:/usr/local/opt/php#7.4/sbin:/usr/local/opt/php#7.4/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/opt/php#7.4/sbin:/usr/local/opt/php#7.4/bin:/opt/local/bin:/opt/local/sbin:/Users/avplat/Library/Android/sdk/tools:/Users/avplat/Library/Android/sdk/platform-tools:/Users/avplat/Developer/flutter/bin:/Users/avplat/Library/Android/sdk/tools:/Users/avplat/Library/Android/sdk/platform-tools:/Users/avplat/Developer/flutter/bin
9 verbose lifecycle AvPlat#0.0.1~lint-fix: CWD: /Users/avplat/Roshan/AvplatV3/avplat-v3
10 silly lifecycle AvPlat#0.0.1~lint-fix: Args: [ '-c', 'bash scripts/lint.sh' ]
11 silly lifecycle AvPlat#0.0.1~lint-fix: Returned: code: 2 signal: null
12 info lifecycle AvPlat#0.0.1~lint-fix: Failed to exec lint-fix script
13 verbose stack Error: AvPlat#0.0.1 lint-fix: `bash scripts/lint.sh`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid AvPlat#0.0.1
15 verbose cwd /Users/avplat/Roshan/AvplatV3/avplat-v3
16 verbose Darwin 20.6.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "lint-fix"
18 verbose node v14.15.5
19 verbose npm v6.14.11
20 error code ELIFECYCLE
21 error errno 2
22 error AvPlat#0.0.1 lint-fix: `bash scripts/lint.sh`
22 error Exit status 2
23 error Failed at the AvPlat#0.0.1 lint-fix script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

Failed at the app#0.0.1 start script. start: `nest start`

I am deploying NestJs app on elastic beanstalk, after successfull deployment, app is not started and shows error at start script but when I login to Amazon Linux 2 ec2 instance and run node dist/main, it start running and not otherwise with npm start.
Logs:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/opt/elasticbeanstalk/node-install/node-v12.19.0-linux-x64/bin/node',
1 verbose cli '/bin/npm',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.14.8
3 info using node#v12.19.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle unmudl-backend-app#0.0.1~prestart: unmudl-backend-app#0.0.1
6 info lifecycle unmudl-backend-app#0.0.1~start: unmudl-backend-app#0.0.1
7 verbose lifecycle unmudl-backend-app#0.0.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle unmudl-backend-app#0.0.1~start: PATH: /opt/elasticbeanstalk/node-install/node-v12.19.0-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/app/current/node_modules/.bin:/sbin:/bin:/usr/sbin:/usr/bin
9 verbose lifecycle unmudl-backend-app#0.0.1~start: CWD: /var/app/current
10 silly lifecycle unmudl-backend-app#0.0.1~start: Args: [ '-c', 'nest start' ]
11 silly lifecycle unmudl-backend-app#0.0.1~start: Returned: code: 1 signal: null
12 info lifecycle unmudl-backend-app#0.0.1~start: Failed to exec start script
13 verbose stack Error: unmudl-backend-app#0.0.1 start: `nest start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/opt/elasticbeanstalk/node-install/node-v12.19.0-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess.<anonymous> (/opt/elasticbeanstalk/node-install/node-v12.19.0-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid unmudl-backend-app#0.0.1
15 verbose cwd /var/app/current
16 verbose Linux 4.14.200-155.322.amzn2.x86_64
17 verbose argv "/opt/elasticbeanstalk/node-install/node-v12.19.0-linux-x64/bin/node" "/bin/npm" "start"
18 verbose node v12.19.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error unmudl-backend-app#0.0.1 start: `nest start`
22 error Exit status 1
23 error Failed at the unmudl-backend-app#0.0.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
You need to change the value of your "start" in package.json to "npm i -g #nestjs/cli && node dist/main"
it should look like the following line:
"start": "npm i -g #nestjs/cli && node dist/main"
and if you are using prisma you will need to do it like:
"start": "npm i -g #prisma/cli #nestjs/cli && prisma generate && node
dist/main"

Failed to exec start script: expo start

So I have installed Node js 12.14.0 and I tried command Expo start after initiating my project but an error appeared.
I checked the log file and that what's in it, even though it was working yesterday.
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.13.4
3 info using node#v12.14.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle #~prestart: #
6 info lifecycle #~start: #
7 verbose lifecycle #~start: unsafe-perm in lifecycle true
8 verbose lifecycle #~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Windows\System32\new-project\node_modules\.bin;C:\Users\Merna Othman\AppData\Roaming\npm;C:\Program Files\nodejs\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Users\Merna Othman\.windows-build-tools\python27\;C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Merna Othman\AppData\Roaming\npm\node_modules\windows-build-tools\node_modules\.bin;C:\Users\Merna Othman\AppData\Roaming\npm\node_modules\.bin;C:\Users\Merna Othman\AppData\Local\Microsoft\WindowsApps;C:\Users\Merna Othman\AppData\Roaming\npm
9 verbose lifecycle #~start: CWD: C:\Windows\System32\new-project
10 silly lifecycle #~start: Args: [ '/d /s /c', 'expo start' ]
11 silly lifecycle #~start: Returned: code: 1 signal: null
12 info lifecycle #~start: Failed to exec start script
13 verbose stack Error: # start: `expo start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:210:5)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:210:5)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid #
15 verbose cwd C:\Windows\System32\new-project
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.14.0
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error # start: `expo start`
22 error Exit status 1
23 error Failed at the # start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Seems to be an issue with Node. Works with Node 12.10, but at least not with Node 12.12 and 12.14. See https://github.com/expo/expo-cli/issues/1147.
I downgraded to Node 12.10 and the error is gone.
I had this same issue. I attempted to just make sure my npm was up-to-date using npm install npm#latest -g from command-line and now the expo issue resolved.

How to fix "ELIFECYCLE" error, during the initial React native setup

Am following the React Native beginner course on udemy, and when following the setting up process, everything works and the builder opens for a few second, then it blackout and I see the Following ERR message
PowerShell Err massege
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\ALi_O\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.13.4
3 info using node#v12.14.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle #~prestart: #
6 info lifecycle #~start: #
7 verbose lifecycle #~start: unsafe-perm in lifecycle true
8 verbose lifecycle #~start: PATH: C:\Users\ALi_O\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\React Native\3.1 rn-starter.zip\rn-starter\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\nodejs\;C:\Users\ALi_O\AppData\Local\Microsoft\WindowsApps;C:\Users\ALi_O\AppData\Roaming\npm
9 verbose lifecycle #~start: CWD: E:\React Native\3.1 rn-starter.zip\rn-starter
10 silly lifecycle #~start: Args: [ '/d /s /c', 'expo start' ]
11 silly lifecycle #~start: Returned: code: 1 signal: null
12 info lifecycle #~start: Failed to exec start script
13 verbose stack Error: # start: `expo start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\ALi_O\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:210:5)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\ALi_O\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:210:5)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid #
15 verbose cwd E:\React Native\3.1 rn-starter.zip\rn-starter
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\ALi_O\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.14.0
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error # start: `expo start`
22 error Exit status 1
23 error Failed at the # start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
It turns out that the latest node.js has problems to work on Windows and the only fix for me was downgrading to Node.js 10.x.
I am running on 10.16.3 and it works all fine:
npm install -g node#10.16.3

react-native npm start fail with log

I am the beginner to the react-native and I got an error while running the AwesomeProject in Android studio. I try running npm start and got the error. Below is the log file. Thank you!
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.12.1
3 info using node#v13.1.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle AwesomeProject#0.0.1~prestart: AwesomeProject#0.0.1
6 info lifecycle AwesomeProject#0.0.1~start: AwesomeProject#0.0.1
7 verbose lifecycle AwesomeProject#0.0.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle AwesomeProject#0.0.1~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\vince\AwesomeProject\node_modules.bin;C:\Python27\;C:\Python27\Scripts;C:\Program Files (x86)\Razer Chroma SDK\bin;C:\Program Files\Razer Chroma SDK\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Program Files\Java\jdk1.8.0_231\bin;C:\Users\vince\AppData\Local\Microsoft\WindowsApps;C:\Users\vince\AppData\Roaming\npm;C:\Users\vince\AppData\Local\Android\Sdk\platform-tools;
9 verbose lifecycle AwesomeProject#0.0.1~start: CWD: C:\Users\vince\AwesomeProject
10 silly lifecycle AwesomeProject#0.0.1~start: Args: [ '/d /s /c', 'react-native start' ]
11 silly lifecycle AwesomeProject#0.0.1~start: Returned: code: 1 signal: null
12 info lifecycle AwesomeProject#0.0.1~start: Failed to exec start script
13 verbose stack Error: AwesomeProject#0.0.1 start: react-native start
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:210:5)
13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:210:5)
13 verbose stack at maybeClose (internal/child_process.js:1028:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid AwesomeProject#0.0.1
15 verbose cwd C:\Users\vince\AwesomeProject
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v13.1.0
19 verbose npm v6.12.1
20 error code ELIFECYCLE
21 error errno 1
22 error AwesomeProject#0.0.1 start: react-native start
22 error Exit status 1
23 error Failed at the AwesomeProject#0.0.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Fixed it.
watchman installation is required:
https://facebook.github.io/watchman/docs/install.html
Did you installed watchman?
Install it from the below link:
https://facebook.github.io/watchman/docs/install.html
I couldn't start react native project.
npm install -g expo-cli
expo init AwesomeProject
cd AwesomeProject
npm start
gives error.
Error log is below.
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\Taner\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'android' ]
2 info using npm#6.14.8
3 info using node#v10.22.0
4 verbose run-script [ 'preandroid', 'android', 'postandroid' ]
5 info lifecycle #~preandroid: #
6 info lifecycle #~android: #
7 verbose lifecycle #~android: unsafe-perm in lifecycle true
8 verbose lifecycle #~android: PATH: C:\Users\Taner\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Taner\Desktop\RoboDezApp\node_modules\.bin;C:\Windows\System32;C:\Users\Taner\AppData\Local\Programs\Python\Python38\Scripts\;C:\Users\Taner\AppData\Local\Programs\Python\Python38\;C:\Program Files\eProsima\fastrtps 2.0.0\bin;C:\Program Files\eProsima\fastrtps 2.0.0\bin\x64Win64VS2017;C:\ProgramData\chocolatey\bin;C:\OpenSSL-Win64\bin\;C:\opencv\x64\vc16\bin;C:\Program Files\CMake\bin;C:\Users\Taner\AppData\Local\Programs\Python\Python38;C:\Python38;C:\Users\Taner\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files\nodejs\;C:\Users\Taner\AppData\Local\Microsoft\WindowsApps;D:\CLion\CLion 2020.1.1\bin;;C:\mingw-w64\mingw32\bin;C:\Users\Taner\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Taner\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Windows\System32;C:\Users\Taner\AppData\Roaming\npm
9 verbose lifecycle #~android: CWD: C:\Users\Taner\Desktop\RoboDezApp
10 silly lifecycle #~android: Args: [ '/d /s /c', 'expo start --android' ]
11 silly lifecycle #~android: Returned: code: 1 signal: null
12 info lifecycle #~android: Failed to exec android script
13 verbose stack Error: # android: `expo start --android`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\Taner\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Taner\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid #
15 verbose cwd C:\Users\Taner\Desktop\RoboDezApp
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Taner\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "android"
18 verbose node v10.22.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error # android: `expo start --android`
22 error Exit status 1
23 error Failed at the # android script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]