I can't install dependencies for React Native Projects correctly - react-native

So I tried running a React Native project in my android emulator using Expo, but every time I install someone else's project, I'm not able to run it.
This is how I install the project along with its dependencies:
> git clone https://github.com/nabendu82/NativeRestaurantSearc.git
> cd NativeRestaurantSearc
> npm install
> npm start
When I run all this, I recieve this error message:
error Invalid regular expression: /(.*\\__fixtures__\\.*|node_modules[\\\]react[\\\]dist[\\\].*|website\\node_modules\\.*|heapCapture\\bundle\.js|.*\\__tests__\\.*)$/: Unterminated character class.
Metro Bundler process exited with code 1
Set EXPO_DEBUG=true in your env to view the stack trace.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # start: `expo start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Yassi\AppData\Roaming\npm-cache\_logs\2020-04-18T10_46_25_411Z-debug.log
This is a complete log of the run:
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\\Yassi\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.13.6
3 info using node#v12.16.1
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\Yassi\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Yassi\Bureaublad\React Native\NativeRestaurantSearc\node_modules\.bin;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Git\cmd;C:\Users\Yassi\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files (x86)\Yarn\bin\;C:\Program Files (x86)\Graphviz2.38\bin\dot.exe;C:\Users\Yassi\AppData\Local\Continuum\anaconda3;C:\Users\Yassi\Ap;C:\Program Files\nodejs\;C:\Users\Yassi\AppData\Local\Continuum\anaconda3;C:\Users\Yassi\AppData\Local\Continuum\anaconda3\Library\mingw-w64\bin;C:\Users\Yassi\AppData\Local\Continuum\anaconda3\Library\usr\bin;C:\Users\Yassi\AppData\Local\Continuum\anaconda3\Library\bin;C:\Users\Yassi\AppData\Local\Continuum\anaconda3\Scripts;C:\Users\Yassi\AppData\Local\Microsoft\WindowsApps;C:\Users\Yassi\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Yassi\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Users\Yassi\AppData\Local\Yarn\bin;C:\Users\Yassi\AppData\Local\Continuum\anaconda3\Library\bin\graphviz;C:\Users\Yassi\Documents\stardog-7.0.1;C:\Users\Yassi\AppData\Roaming\npm
9 verbose lifecycle #~start: CWD: C:\Users\Yassi\Bureaublad\React Native\NativeRestaurantSearc
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\Yassi\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:311:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Yassi\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:311: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\Yassi\Bureaublad\React Native\NativeRestaurantSearc
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Yassi\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.16.1
19 verbose npm v6.13.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 think this has to do with npm not installing the dependencies correctly. There must be going something wrong when I do this, because this is the message I recieve when I run npm install:
added 809 packages from 438 contributors and audited 37723 packages in 119.347s
found 1072 low severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
What can I do to fix this? I tried reinstalling npm but that doesn't work.

Related

How can I fix these errors with npm run build on the Next.js default project?

I'm a graphic student trying to learn something further than classic HTML/CSS.
I want to build the default Next.js app, which you can get by npm create-next-app filename.
It certainly works when npm run dev. I can see the index page on localhost:3000.
But npm run build gets:
% npm run build
> test#0.1.0 build /Users/minori/Documents/portfolio/test
> next build
info - Checking validity of types
Failed to compile.
./pages/index.js
8:7 Error: Missing "key" prop for element in array react/jsx-key
/*almost same messages repeated for every line*/
63:13 Error: Missing "key" prop for element in array react/jsx-key
info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test#0.1.0 build: `next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the test#0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/minori/.npm/_logs/2022-02-25T17_53_21_317Z-debug.log
And here is the debug log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.15
3 info using node#v14.17.6
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle test#0.1.0~prebuild: test#0.1.0
6 info lifecycle test#0.1.0~build: test#0.1.0
7 verbose lifecycle test#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle test#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/minori/Documents/portfolio/test/node_modules/.bin:/Users/minori/.npm-global/lib/node_modules/n/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/minori/bin:/opt/osxws/bin:/opt/osxws/sbin
9 verbose lifecycle test#0.1.0~build: CWD: /Users/minori/Documents/portfolio/test
10 silly lifecycle test#0.1.0~build: Args: [ '-c', 'next build' ]
11 silly lifecycle test#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle test#0.1.0~build: Failed to exec build script
13 verbose stack Error: test#0.1.0 build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/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> (/usr/local/lib/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:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid test#0.1.0
15 verbose cwd /Users/minori/Documents/portfolio/test
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.17.6
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error test#0.1.0 build: `next build`
22 error Exit status 1
23 error Failed at the test#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 ]
I already tried npm install -g npm-rm -rf node_modules-npm install, re-installing node.js, npm cache clear --force and rm package-lock.json.
Does anyone know what the problem is?
What else can I try now?
It's not you, there is an issue logged with eslint-plugin-react that create-next-app uses, if they haven't already done so (try npm create-next-app again) you can find eslint-plugin-react in your package.json to version 7.29.1
You can see the Vercel team noting the change and the eslint-plugin-react author's responding
https://github.com/yannickcr/eslint-plugin-react/issues/3215#issuecomment-1051115159

erro:This is probably not a problem with npm. There is likely additional logging output above

In my project, I'm using VueCli for the frontend. Now what I'm trying to do is deploy my project which is in remote server into the actual server. I'm using npm run build command to build the frontend first. But I can't build my project since the following error occurs again and again
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mobile-h5#0.1.0 build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mobile-h5#0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/daisywu/.npm/_logs/2021-09-24T06_13_06_000Z-debug.log
I delete package-lock.json and node_modules,then do npm cache clean --force,then do npm install,Still unable to construct
debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.9
3 info using node#v14.15.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mobile-h5#0.1.0~prebuild: mobile-h5#0.1.0
6 info lifecycle mobile-h5#0.1.0~build: mobile-h5#0.1.0
7 verbose lifecycle mobile-h5#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle mobile-h5#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/daisywu/Documents/mobile-h5/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle mobile-h5#0.1.0~build: CWD: /Users/daisywu/Documents/mobile-h5
10 silly lifecycle mobile-h5#0.1.0~build: Args: [ '-c', 'vue-cli-service build' ]
11 silly lifecycle mobile-h5#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle mobile-h5#0.1.0~build: Failed to exec build script
13 verbose stack Error: mobile-h5#0.1.0 build: `vue-cli-service build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/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.<anonymous> (/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 mobile-h5#0.1.0
15 verbose cwd /Users/daisywu/Documents/mobile-h5
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.15.3
19 verbose npm v6.14.9
20 error code ELIFECYCLE
21 error errno 1
22 error mobile-h5#0.1.0 build: `vue-cli-service build`
22 error Exit status 1
23 error Failed at the mobile-h5#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 ]
Please help thank you
The reason is insufficient memory. Update the answer for your reference
Written in package.json
"build": "node --max_old_space_size=4096 node_modules/#vue/cli-service/bin/vue-cli-service.js build --mode development"
do npm run build

Webpack error compiling theme in Prestashop

Trying to compile theme (named foo) in Prestashop:
cd themes/foo/_dev
npm run build
Get the following error.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! prestashop-classic-dev-tools#1.0.0 build: `webpack`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the prestashop-classic-dev-tools#1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-07-02T05_58_35_445Z-debug.log
Here is the log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.14.13
3 info using node#v14.17.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle prestashop-classic-dev-tools#1.0.0~prebuild: prestashop-classic-dev-tools#1.0.0
6 info lifecycle prestashop-classic-dev-tools#1.0.0~build: prestashop-classic-dev-tools#1.0.0
7 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: PATH: /usr/lib/node_modules/npm/node_mod$
9 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: CWD: /var/www/html/themes/foo$
10 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Args: [ '-c', 'webpack' ]
11 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Returned: code: 2 signal: null
12 info lifecycle prestashop-classic-dev-tools#1.0.0~build: Failed to exec build script
13 verbose stack Error: prestashop-classic-dev-tools#1.0.0 build: `webpack`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at EventEmitter.emit (events.js:376:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at ChildProcess.emit (events.js:376:20)
13 verbose stack at maybeClose (internal/child_process.js:1055: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 /var/www/html/themes/foo/_dev
16 verbose Linux 5.8.0-59-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v14.17.0
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 2
22 error prestashop-classic-dev-tools#1.0.0 build: `webpack`
22 error Exit status 2
23 error Failed at the prestashop-classic-dev-tools#1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
npm version is:
> npm -v
6.14.13
What could be the cause?
Cause of the issue not found. Resolved with the following commands:
Clean npm cache
> npm cache clean --force
Remove node modules
> rm -rf node_modules package-lock.json
Install npm
> npm install
Run build
> npm run build

IBM blockchain platform Visual Studio Code : Error while Packaging Smart Contract

I'm having trouble figuring out the issue while packaging Smart Contract on the IBM Blockchain Platform on Visual Studio Code. I installed the following:
Node.js v14.16.0
npm 6.14.11
Docker version 19.03.13, build cd8016b6bc
docker-compose version 1.25.5, build unknown
I successfully create a new smart contract project. When I ram command - package open project in Command Pallete.
I received this error message:
> Executing task in folder demoContract: npm run build <
> demoContract#0.0.1 build /home/shubham14/Desktop/Major project - blockchain/demoContract
> tsc
sh: 1: tsc: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! demoContract#0.0.1 build: `tsc`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the demoContract#0.0.1 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /home/shubham14/.npm/_logs/2021-03-03T11_38_29_505Z-debug.log
The terminal process "/bin/bash '-c', 'npm run build'" terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.
**Debug-log :**
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.11
3 info using node#v14.16.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle demoContract#0.0.1~prebuild: demoContract#0.0.1
6 info lifecycle demoContract#0.0.1~build: demoContract#0.0.1
7 verbose lifecycle demoContract#0.0.1~build: unsafe-perm in lifecycle true
8 verbose lifecycle demoContract#0.0.1~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/shubham14/Desktop/Major project - blockchain/demoContract/node_modules/.bin:/home/shubham14/Desktop/jdk-14/bin:/home/shubham14/anaconda3/lib/graphviz:/home/apache-maven-3.6.3/bin:/home/shubham14/anaconda3/bin:/home/shubham14/anaconda3/condabin:/home/shubham14/jdk-14_linux-x64_bin/jdk-14/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle demoContract#0.0.1~build: CWD: /home/shubham14/Desktop/Major project - blockchain/demoContract
10 silly lifecycle demoContract#0.0.1~build: Args: [ '-c', 'tsc' ]
11 info lifecycle demoContract#0.0.1~build: Failed to exec build script
12 verbose stack Error: demoContract#0.0.1 build: `tsc`
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:315:20)
12 verbose stack at maybeClose (internal/child_process.js:1048:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
13 verbose pkgid demoContract#0.0.1
14 verbose cwd /home/shubham14/Desktop/Major project - blockchain/demoContract
15 verbose Linux 5.4.0-42-generic
16 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
17 verbose node v14.16.0
18 verbose npm v6.14.11
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error demoContract#0.0.1 build: `tsc`
23 error spawn ENOENT
24 error Failed at the demoContract#0.0.1 build script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
Try running npm install first (and maybe even reloading VS Code afterwards).

Getting error "botium-cli is not recognized as an internal or external command, operable program or batch file"

I have a project in WebStorm with botium tests. My developer has helped me open the project and the configuration for test:botium:local. When I press the run for test:botium:local, I should get the results of botium tests. I am on Windows 10.
Instead I get this output:
"C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" run test:botium:local --scripts-prepend-node-path=auto
> chatbot-backend#1.0.0 test:botium:local C:\Users\julie\Botium\<my repo>
> botium-cli run --config botium.local.json --convos botium/convos
'botium-cli' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! chatbot-backend#1.0.0 test:botium:local: `botium-cli run --config botium.local.json --convos botium/convos `
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chatbot-backend#1.0.0 test:botium:local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\julie\AppData\Roaming\npm-cache\_logs\2019-08-29T23_17_10_452Z-debug.log
Process finished with exit code 1
In my system environment variables, under edit environment variable, I have C:\Program Files\nodejs\
If I type npm -v in my terminal, I see that it's on 6.4.16.4.1
If I type botium-cli -V in my terminal, I get 'botium-cli' is not recognized as an internal or external command, operable program or batch file
If I reinstall through npm install -g botium-cli on my terminal, it appears to download again and says botium-cli##0.0.53 at the end, updated 1 package
If I go to My C:\users\julie\AppData\Roaming\npm\node_modules there is a botium-cli folder
If I open my command line, by default I'm in Program Files\nodejs and if I type botium-cli -V I get back 0.0.530.0.53
If I navigate to the Users/julie/Botium folder where my project is and type botium-cli -V, I get back the not recognized error even though I can download it there on powershell
The edit configuration script is: "test:botium:local": "./botiumChangeConfigUrls.sh botium.json botium.local.json && botium-cli run --config botium.local.json --convos botium/convos ",
I've rebooted my PC
I've looked all over stack overflow and google
Here is the log file mentioned in the terminal:
0 info it worked if it ends with ok
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 'test:botium:local',
1 verbose cli '--scripts-prepend-node-path=auto' ]
2 info using npm#6.4.1
3 info using node#v10.11.0
4 verbose run-script [ 'pretest:botium:local',
4 verbose run-script 'test:botium:local',
4 verbose run-script 'posttest:botium:local' ]
5 info lifecycle chatbot-backend#1.0.0~pretest:botium:local: chatbot-backend#1.0.0
6 info lifecycle chatbot-backend#1.0.0~test:botium:local: chatbot-backend#1.0.0
7 verbose lifecycle chatbot-backend#1.0.0~test:botium:local: unsafe-perm in lifecycle true
8 verbose lifecycle chatbot-backend#1.0.0~test:botium:local: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\julie\Botium\chatbot-poc\node_modules\.bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Docker\Docker\Resources\bin;C:\app\julie\virtual\product\12.2.0\dbhome_1\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Users\julie\AppData\Local\Android\Sdk\tools\bin;C:\Users\julie\AppData\Local\Android\Sdk\tools;C:\Users\julie\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\PICT\;C:\Program Files\Java\jdk1.8.0_171\bin;C:\Maven\apache-maven-3.6.1\bin;C:\Python27;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\nodejs\;C:\Users\julie\ApacheJmeter\apache-jmeter-5.0\bin;C:\Program Files\Git\cmd;C:\Program Files\PuTTY\;C:\Program Files\nodejs\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Users\julie\AppData\Local\Android\Sdk\tools\bin;C:\Users\julie\AppData\Local\Android\Sdk\tools;C:\Users\julie\AppData\Local\Android\Sdk\platform-tools;C:\Program Files\Git\cmd;C:\Program Files (x86)\PICT\;C:\Program Files\Java\jdk1.8.0_171\bin;C:\Maven\apache-maven-3.5.4-bin\apache-maven-3.5.4\bin;C:\Python27;C:\Ruby24-x64\bin;C:\Users\julie\AppData\Local\GitHubDesktop\bin;C:\Users\julie\AppData\Local\Microsoft\WindowsApps;C:\Users\julie\AppData\Local\atom\bin;C:\Users\julie\eclipse-workspace\SceneBuilder\jtds\jtds-1.3.1.jar;;C:\Users\julie\AppData\Local\Microsoft\WindowsApps;C:\Users\julie\AppData\Local\Programs\Microsoft VS Code\bin
9 verbose lifecycle chatbot-backend#1.0.0~test:botium:local: CWD: C:\Users\julie\Botium\chatbot-poc
10 silly lifecycle chatbot-backend#1.0.0~test:botium:local: Args: [ '/d /s /c',
10 silly lifecycle 'botium-cli run --config botium.local.json --convos botium/convos ' ]
11 silly lifecycle chatbot-backend#1.0.0~test:botium:local: Returned: code: 1 signal: null
12 info lifecycle chatbot-backend#1.0.0~test:botium:local: Failed to exec test:botium:local script
13 verbose stack Error: chatbot-backend#1.0.0 test:botium:local: `botium-cli run --config botium.local.json --convos botium/convos `
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:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
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:182:13)
13 verbose stack at maybeClose (internal/child_process.js:962:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid chatbot-backend#1.0.0
15 verbose cwd C:\Users\julie\Botium\chatbot-poc
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "test:botium:local" "--scripts-prepend-node-path=auto"
18 verbose node v10.11.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error chatbot-backend#1.0.0 test:botium:local: `botium-cli run --config botium.local.json --convos botium/convos `
22 error Exit status 1
23 error Failed at the chatbot-backend#1.0.0 test:botium:local script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
In case it helps anyone, I re-ran an npm install and then npm run in the folder where my project was seemed to fix the issue
Add C:\users\julie\AppData\Roaming\npm to your %PATH% environment variable.