Vue Cli 3 Npm Run Build Error: Callback was already called - vue.js

Everything works fine until this error shows out. I can run npm run serve with no problem except npm run build.
Here's the error log
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 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm#6.14.15
3 info using node#v14.18.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mop_client2#0.1.0~prebuild: mop_client2#0.1.0
6 info lifecycle mop_client2#0.1.0~build: mop_client2#0.1.0
7 verbose lifecycle mop_client2#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle mop_client2#0.1.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\xampp\htdocs\mop\mataonlineportalclient\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\xampp\php;C:\Program Files\PuTTY\;C:\Program Files\nodejs\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\ProgramData\ComposerSetup\bin;C:\Users\Predator Onii\AppData\Local\Microsoft\WindowsApps;;C:\Users\Predator Onii\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Predator Onii\AppData\Roaming\Composer\vendor\bin;C:\Users\Predator Onii\AppData\Roaming\npm
9 verbose lifecycle mop_client2#0.1.0~build: CWD: C:\xampp\htdocs\mop\mataonlineportalclient
10 silly lifecycle mop_client2#0.1.0~build: Args: [ '/d /s /c', 'vue-cli-service build' ]
11 silly lifecycle mop_client2#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle mop_client2#0.1.0~build: Failed to exec build script
13 verbose stack Error: mop_client2#0.1.0 build: `vue-cli-service build`
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:400:28)
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:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1058:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid mop_client2#0.1.0
15 verbose cwd C:\xampp\htdocs\mop\mataonlineportalclient
16 verbose Windows_NT 10.0.19043
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v14.18.0
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error mop_client2#0.1.0 build: `vue-cli-service build`
22 error Exit status 1
23 error Failed at the mop_client2#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Here's what I did so far:
npm cache clean -f
npm install
check out to another branch to see if I did something wrong with my code.
None of these fixes solved the problem.
I don't know what causes the problem it's been 4 days already. Please help.

I found an answer and tried module.exports = { css: { extract: false } } to vue.config.js hope it helps everyone.

Related

webpack-cli TypeError: compiler.plugin is not a function

I'm totally new to prestashop development and all of that stuff and if u reply pls use simplest explanation possible. I'm actually new to web tech too. There is a problem with webpack when im trying to use 'npm run watch' and it says
[webpack-cli] TypeError: compiler.plugin is not a function
at ExtractTextPlugin.apply (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\extract-text-webpack-plugin\index.js:233:11)
at createCompiler (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\webpack.js:69:12)
at create (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\webpack.js:113:15)
at webpack (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\webpack.js:121:46)
at f (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack\lib\index.js:37:15)
at WebpackCLI.createCompiler (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:1337:24)
at async WebpackCLI.bundleCommand (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:1433:20)
at async Command. (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:384:25)
at async Promise.all (index 1)
at async Command. (C:\xampp\htdocs\prestashop\themes\classic_dev\node_modules\webpack-cli\lib\webpack-cli.js:824:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! prestashop-classic-dev-tools#1.0.0 watch: webpack --progress --watch
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the prestashop-classic-dev-tools#1.0.0 watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
the complete log is
> 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 'run',
1 verbose cli 'watch'
1 verbose cli ]
2 info using npm#6.14.10
3 info using node#v14.15.4
4 verbose run-script [ 'prewatch', 'watch', 'postwatch' ]
5 info lifecycle prestashop-classic-dev-tools#1.0.0~prewatch: prestashop-classic-dev-tools#1.0.0
6 info lifecycle prestashop-classic-dev-tools#1.0.0~watch: prestashop-classic-dev-tools#1.0.0
7 verbose lifecycle prestashop-classic-dev-tools#1.0.0~watch: unsafe-perm in lifecycle true
8 verbose lifecycle prestashop-classic-dev-tools#1.0.0~watch: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\xampp\htdocs\prestashop\themes\classic\_dev\node_modules\.bin;C:\Users\ja\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\ja\bin;C:\Python39\Scripts;C:\Python39;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\Git\cmd;C:\Program Files\nodejs;C:\Program Files\MySQL\MySQL Server 8.0\bin;C:\Program Files\MySQL\MySQL Shell 8.0\bin;C:\Users\ja\AppData\Local\Programs\Python\Python38\Scripts;C:\Users\ja\AppData\Local\Programs\Python\Python38;C:\Users\ja\geckodriver.exe;C:\Users\ja\AppData\Local\Microsoft\WindowsApps;C:\Users\ja\AppData\Local\Programs\Microsoft VS Code\bin;C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin;C:\Users\ja\.pyenv\pyenv-win\bin;C:\Users\ja\.pyenv\pyenv-win\shims;C:\xampp\php;C:\Users\ja\AppData\Roaming\npm;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle prestashop-classic-dev-tools#1.0.0~watch: CWD: C:\xampp\htdocs\prestashop\themes\classic\_dev
10 silly lifecycle prestashop-classic-dev-tools#1.0.0~watch: Args: [ '/d /s /c', 'webpack --progress --watch' ]
11 silly lifecycle prestashop-classic-dev-tools#1.0.0~watch: Returned: code: 2 signal: null
12 info lifecycle prestashop-classic-dev-tools#1.0.0~watch: Failed to exec watch script
13 verbose stack Error: prestashop-classic-dev-tools#1.0.0 watch: `webpack --progress --watch`
13 verbose stack Exit status 2
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:315:20)
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: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 prestashop-classic-dev-tools#1.0.0
15 verbose cwd C:\xampp\htdocs\prestashop\themes\classic\_dev
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "watch"
18 verbose node v14.15.4
19 verbose npm v6.14.10
20 error code ELIFECYCLE
21 error errno 2
22 error prestashop-classic-dev-tools#1.0.0 watch: `webpack --progress --watch`
22 error Exit status 2
23 error Failed at the prestashop-classic-dev-tools#1.0.0 watch script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
I already tried to reinstall Node and webpack and also tried to run this with my antivirus off but nothing seems to work

How do I resolve this recurring error when I run npm start?

I started with:
Installing Node.js on my Windows 10 System (I installed v12.18.3)
Then I ran command: npm i -g expo-cli
to install expo on my system
Next I ran expo init demoProject
Next I changed directory into the demoProject (C:\Users\vridd>cd DoneWithIt)
Next I used command code . to start Visual Studio and in the terminal in VS Code, I ran npm start
As soon as I run this, I keep getting this issue. Please help!
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.14.6
3 info using node#v12.18.3
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:\Users\vridd\DoneWithIt\node_modules\.bin;C:\Program Files\Java\jdk-14.0.1\bin;C:\Program Files\nodejs\;C:\Program Files\Java\jdk-14.0.1\bin;C:\Program Files\nodejs\;;C:\Users\vridd\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\vridd\AppData\Roaming\npm
9 verbose lifecycle #~start: CWD: C:\Users\vridd\DoneWithIt
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:315:20)
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:315: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 #
15 verbose cwd C:\Users\vridd\DoneWithIt
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.18.3
19 verbose npm v6.14.6
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 ]
I solved this by updating to the latest npm version (npm install latest-version) and doing an npm update on my project. From what I could tell from searching, it seems that some versions of Node and NPM don't play well together.

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 ]