Zoom Meeting Web SDK "npm start" error

Meeting SDK Web
1

When I run npm start, I encounter the following problem.

events.js:292
throw er; // Unhandled ‘error’ event
^

Error: spawn chrome ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted ‘error’ event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -2,
code: ‘ENOENT’,
syscall: ‘spawn chrome’,
path: ‘chrome’,
spawnargs: [ ‘https://xxxxx.com:9999/index.html’ ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! websdk-cdn@2.9.0 start: set NODE_ENV=development && set BABEL_ENV=development && node corp.js --corp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the websdk-cdn@2.9.0 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! /root/.npm/_logs/2023-03-06T11_23_23_775Z-debug.log

2

This is the content of the log file:

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/local/nodejs/bin/node’, ‘/usr/local/bin/npm’, ‘start’ ]
2 info using npm@6.14.12
3 info using node@v14.16.1
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle websdk-cdn@2.9.0~prestart: websdk-cdn@2.9.0
6 info lifecycle websdk-cdn@2.9.0~start: websdk-cdn@2.9.0
7 verbose lifecycle websdk-cdn@2.9.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle websdk-cdn@2.9.0~start: PATH: /usr/local/nodejs/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/ajitasap/Zoom-Web-SDK-2.9.0/node_modules/.bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/ajitasap/.local/bin:/home/ajitasap/bin
9 verbose lifecycle websdk-cdn@2.9.0~start: CWD: /home/ajitasap/Zoom-Web-SDK-2.9.0
10 silly lifecycle websdk-cdn@2.9.0~start: Args: [
10 silly lifecycle ‘-c’,
10 silly lifecycle ‘set NODE_ENV=development && set BABEL_ENV=development && node corp.js --corp’
10 silly lifecycle ]
11 silly lifecycle websdk-cdn@2.9.0~start: Returned: code: 1 signal: null
12 info lifecycle websdk-cdn@2.9.0~start: Failed to exec start script
13 verbose stack Error: websdk-cdn@2.9.0 start: set NODE_ENV=development && set BABEL_ENV=development && node corp.js --corp
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/nodejs/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/nodejs/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 websdk-cdn@2.9.0
15 verbose cwd /home/ajitasap/Zoom-Web-SDK-2.9.0
16 verbose Linux 3.10.0-1160.24.1.el7.x86_64
17 verbose argv “/usr/local/nodejs/bin/node” “/usr/local/bin/npm” “start”
18 verbose node v14.16.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error websdk-cdn@2.9.0 start: set NODE_ENV=development && set BABEL_ENV=development && node corp.js --corp
22 error Exit status 1
23 error Failed at the websdk-cdn@2.9.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 ]

3

@kavita.agarwal Here are the sessions regarding WebSDK Integrations

4

I am using nodejs.

errno: -2,
code: ‘ENOENT’,
syscall: ‘spawn chrome’,
path: ‘chrome’,

5

@kavita.agarwal

In the above sessions, all the Zoom WebSDK integration demos are done.

6

Yes, I watched those videos but it didn’t solve my problem, I just downloaded the Web SDK 2.10.1 and then changed the port, domain name and certificate. But when I run “npm start”, it reports the above error. Please help. Thanks

7

Hi @kavita.agarwal
Thanks for reaching out to us.
Are you still experiencing this issue?

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.