Problem with running Zoom Web SDK application

I have a problem with Zoom SDK Web, when I run the application with the npm run start command line I get errors:

websdk-local@1.9.5 start
set NODE_ENV=development && set BABEL_ENV=development && webpack serve --config webpack.config.dev.js
sh: 1: webpack: not found

Here is the screenshot :

How could I correct this error?

Thank you in advance for your answers.

Hi @epenyblaise,

Have you ran npm install before doing this? The webpack module is missing currently.

Thanks,
Alex

I have issue with npm run start

websdk-local@1.9.5 start /home/centos/sunstone-ui/sample-app-web/Local
set NODE_ENV=development && set BABEL_ENV=development && webpack serve --config webpack.config.dev.js

https false
disableCORP true
:information_source: 「wds」: Project is running at http://0.0.0.0:9999/
:information_source: 「wds」: webpack output is served from /static
:information_source: 「wds」: Content not from webpack is served from /home/centos/sunstone-ui/sample-app-web/Local
events.js:174
throw er; // Unhandled ‘error’ event
^

Error: spawn chrome ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
Emitted ‘error’ event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
[… lines matching original stack trace …]
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! websdk-local@1.9.5 start: set NODE_ENV=development && set BABEL_ENV=development && webpack serve --config webpack.config.dev.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the websdk-local@1.9.5 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! /home/centos/.npm/_logs/2021-05-23T03_37_37_009Z-debug.log

Same error im also getting, when I run the application with the npm run start command line I get errors:

i install npm also (npm install)

websdk-local@1.9.5 start /home/userName/Documents/code/hack/sample-app-web/Local
set NODE_ENV=development && set BABEL_ENV=development && webpack serve --config webpack.config.dev.js

https false
disableCORP true
:information_source: 「wds」: Project is running at http://0.0.0.0:9999/
:information_source: 「wds」: webpack output is served from /static
:information_source: 「wds」: Content not from webpack is served from /home/varun/Documents/code/hack/sample-app-web/Local
events.js:292
throw er; // Unhandled ‘error’ event
^

Error: spawn chrome ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted ‘error’ event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: ‘ENOENT’,
code: ‘ENOENT’,
syscall: ‘spawn chrome’,
path: ‘chrome’,
spawnargs: [ ‘http://127.0.0.1:9999’ ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! websdk-local@1.9.5 start: set NODE_ENV=development && set BABEL_ENV=development && webpack serve --config webpack.config.dev.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the websdk-local@1.9.5 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! /home/userName/.npm/_logs/2021-05-23T07_33_56_833Z-debug.log

Hey @varsha.lodha , @vaarunkumar13 , @epenyblaise ,

Thanks for reporting this. We will investigate and get back to you.

-Tommy

Hey @varsha.lodha , @vaarunkumar13 , @epenyblaise ,

I was not able to reproduce this issue. I cloned the sample app, then ran npm install inside the /sample-app-web/Local directory, and then ran npm run start.

Here is my output:

$ npm run start

> websdk-local@1.9.5 start
> set NODE_ENV=development && set BABEL_ENV=development && webpack serve --config webpack.config.dev.js

https false
disableCORP true
ℹ 「wds」: Project is running at http://0.0.0.0:9999/
ℹ 「wds」: webpack output is served from /static
ℹ 「wds」: Content not from webpack is served from /Users/tommygaessler/Code/sample-app-web/Local
ℹ 「wdm」: asset index.min.js 4.52 MiB [emitted] (name: index)
asset meeting.min.js 4.52 MiB [emitted] (name: meeting)
runtime modules 51.7 KiB 26 modules
modules by path ./ 4.37 MiB
  modules by path ./node_modules/ 4.36 MiB 30 modules
  modules by path ./js/*.js 7.81 KiB
    ./js/index.js 4.8 KiB [built] [code generated]
    ./js/meeting.js 3.01 KiB [built] [code generated]
external "React" 42 bytes [built] [code generated]
external "ReactDOM" 42 bytes [built] [code generated]
external {"commonjs":"lodash","amd":"lodash","root":"_","var":"_"} 42 bytes [built] [code generated]
external "Redux" 42 bytes [built] [code generated]
external "ReduxThunk" 42 bytes [built] [code generated]
webpack 5.28.0 compiled successfully in 3327 ms
ℹ 「wdm」: Compiled successfully.

Make sure you are running npm install inside the Local directory.

Thanks,
Tommy

1 Like

Hi @tommy , @alexmayo ,

I ran npm install inside the Local directory and then when I ran npm run start command line I no longer get error.

Thank you for help

1 Like

Hi @vaarunkumar13 , @varsha.lodha ,

You need just ran npm install inside /sample-app-web/CDN and then ran npm run start.

Here is my output :

      npm run start
      > websdk-cdn@1.9.5 start
      > concurrently "http-server -a 0.0.0.0 -p 9999 -c-1 -o index.html"
      [0] Starting up http-server, serving ./
      [0] Available on:
      [0]   http://192.168.56.1:9999
      [0]   http://127.0.0.1:9999
      [0]   http://192.168.1.50:9999
      [0] Hit CTRL-C to stop the server
      [0] open: http://127.0.0.1:9999/index.html
      [0] [2021-05-25T13:59:15.327Z]  "GET /" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) 
      AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"
      [0] (node:194) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers 
      is deprecated
      [0] (Use `node --trace-deprecation ...` to show where the warning was created)
      [0] [2021-05-25T13:59:15.934Z]  "GET /js/vconsole.min.js" "Mozilla/5.0 (Windows NT 
      10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36"
      [0] [2021-05-25T13:59:15.940Z]  "GET /js/tool.js" "Mozilla/5.0 (Windows NT 10.0; 
      Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36"
      [0] [2021-05-25T13:59:15.956Z]  "GET /js/index.js" "Mozilla/5.0 (Windows NT 10.0; 
      Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36"
      [0] [2021-05-25T13:59:22.753Z]  "GET /favicon.ico" "Mozilla/5.0 (Windows NT 10.0; 
      Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36"
      [0] [2021-05-25T13:59:23.617Z]  "GET /index.html" "Mozilla/5.0 (Windows NT 10.0; 
      Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36 Edg/90.0.818.66"
      [0] [2021-05-25T13:59:24.474Z]  "GET /js/tool.js" "Mozilla/5.0 (Windows NT 10.0; 
      Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36 Edg/90.0.818.66"
      [0] [2021-05-25T13:59:24.487Z]  "GET /js/vconsole.min.js" "Mozilla/5.0 (Windows NT 
     10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36 Edg/90.0.818.66"
     [0] [2021-05-25T13:59:24.685Z]  "GET /js/index.js" "Mozilla/5.0 (Windows NT 10.0; 
     Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
    Safari/537.36 Edg/90.0.818.66"
     [0] [2021-05-25T13:59:35.602Z]  "GET /favicon.ico" "Mozilla/5.0 (Windows NT 10.0; 
     Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 
      Safari/537.36 Edg/90.0.818.66"

Hi @epenyblaise,

This is fine and is the expected output.

Thanks,
Alex

1 Like

Let us know if you have any questions @epenyblaise

Max

2 Likes

Hi @MaxM,

I have question not for this topic but for another topic.

It is obligated to generate signature from backend for join meetings and join webinar ?

I created another topic for this because i have issue, when i ran node function.js i get errors :

buffer.js:329
throw new ERR_INVALID_ARG_TYPE(
^
TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an 
instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received type number 
(NaN)
    at Function.from (buffer.js:329:9)
    at generateSignature (/mnt/c/Users/epeny/zoom-sdk-web-1.9.5/CDN/function.js:21:22)
    at Object.<anonymous> (/mnt/c/Users/epeny/zoom-sdk-web- 
     1.9.5/CDN/function.js:29:13)
    at Module._compile (internal/modules/cjs/loader.js:1251:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1272:10)
    at Module.load (internal/modules/cjs/loader.js:1100:32)
    at Function.Module._load (internal/modules/cjs/loader.js:962:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47 {
          code: 'ERR_INVALID_ARG_TYPE'
     }

Hi @epenyblaise,

Yes, you will need to generate your signature from your backend. And this is required for joining/starting Webinars via Web SDK.

Let us know if you have questions about this.

Thanks,
Will

Hi @will.zoom,

I will generate the signature from the backend to join / start webinars through the Web SDK.

At the moment I have no questions on this topic, but I might have questions on another topic, since I am using the Zoom API for the first time.

Thanks for your answer.

I’m glad that helped! I’ll go ahead and close this topic now but feel free to open a new topic if you encounter any further issues or questions.

Max