Openvidu-call angular client side can not run

Issues with deployments
1

Hi guys,
I’m try to run OpenVidu locally in Windows 10. I downloaded openvidu-local-deployment and openvidu-call. The community version of openvidu-local-deployment has been successfully run.

However, it failed when trying to start the openvidu-call client side.

The following is the error message.

screenshot-20240929-135122
screenshot-20240929-135122999×1031 21.6 KB

Below are some of my environments.

C:\Users\Administrator>node -v
v18.20.4

C:\Users\Administrator>npm -v
10.8.3

C:\Users\Administrator>ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI: 18.2.6
Node: 18.20.4
Package Manager: npm 10.8.3
OS: win32 x64

Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1802.6 (cli-only)
@angular-devkit/core         18.2.6 (cli-only)
@angular-devkit/schematics   18.2.6 (cli-only)
@schematics/angular          18.2.6 (cli-only)
2

Hi @Qeezy ,

you should clone the openvidu-call repo from tag 3.0.0-beta2. This should work for you

git clone https://github.com/OpenVidu/openvidu-call.git -b v3.0.0-beta2
3

Thanks @CSantosM
But still not working.

D:\Other\OpenVidu\openvidu-call\openvidu-call-front>npm install
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@rollup\plugin-json\dist\cjs\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@rollup\plugin-json\dist\cjs\index.js.DELETE.dbffd02ce4f9804d5d6093786eb5c9d7'
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@rollup\pluginutils\dist\cjs\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@rollup\pluginutils\dist\cjs\index.js.DELETE.0ad9198b4a2529e4c5a0618d787bf954'
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\socks-proxy-agent\dist\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\socks-proxy-agent\dist\index.js.DELETE.c1a4f028d2d6ec7e0018f444ef533360'
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\https-proxy-agent\dist\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\https-proxy-agent\dist\index.js.DELETE.07a95c287114418cb8b620760e0b82dd'
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\http-proxy-agent\dist\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\http-proxy-agent\dist\index.js.DELETE.0c18ce5da0de2ea8f2f21f6b7354481d'
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@inquirer\figures\dist\cjs\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@inquirer\figures\dist\cjs\index.js.DELETE.f18acd3d027c250702d6339de9e45395'
npm warn tar TAR_ENTRY_ERROR EXDEV: cross-device link not permitted, rename 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\agent-base\dist\index.js' -> 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\agent-base\dist\index.js.DELETE.e2c38259de3b796095def25a5f3a0c24'
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated chromedriver@106.0.1: Chromedriver download url has changed. Use version 114.0.2 or newer.
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated tslint@6.1.3: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm warn cleanup Failed to remove some directories [
npm warn cleanup   [
npm warn cleanup     'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\chromedriver',
npm warn cleanup     [Error: EBUSY: resource busy or locked, rmdir 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\chromedriver'] {
npm warn cleanup       errno: -4082,
npm warn cleanup       code: 'EBUSY',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\chromedriver'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@angular\compiler-cli\src'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\@angular\\compiler-cli\\src'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\codelyzer',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\codelyzer'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\codelyzer'
npm warn cleanup     }
npm warn cleanup   ],
npm warn cleanup   [
npm warn cleanup     'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\@angular-devkit\\build-angular',
npm warn cleanup     [Error: EPERM: operation not permitted, rmdir 'D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\@angular-devkit\build-angular\node_modules\@angular\build\src\tools'] {
npm warn cleanup       errno: -4048,
npm warn cleanup       code: 'EPERM',
npm warn cleanup       syscall: 'rmdir',
npm warn cleanup       path: 'D:\\Other\\OpenVidu\\openvidu-call\\openvidu-call-front\\node_modules\\@angular-devkit\\build-angular\\node_modules\\@angular\\build\\src\\tools'
npm warn cleanup     }
npm warn cleanup   ]
npm warn cleanup ]
npm error code 1
npm error path D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\lmdb
npm error command failed
npm error command C:\Windows\system32\cmd.exe /d /s /c node-gyp-build-optional-packages
npm error D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\index.js:77
npm error   throw new Error('No native build was found for ' + target + '\n    attempted loading from: ' + dir + ' and package:' +
npm error   ^
npm error
npm error Error: No native build was found for platform=win32 arch=x64 runtime=node abi=108 uv=1 libc=glibc node=18.20.4npm error     attempted loading from: D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\lmdb and package: @lmdb/lmdb-win32-x64
npm error
npm error     at load.path (D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\index.js:77:9)
npm error     at load (D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\index.js:29:25)
npm error     at Object.<anonymous> (D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\build-test.js:19:19)
npm error     at Module._compile (node:internal/modules/cjs/loader:1364:14)
npm error     at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
npm error     at Module.load (node:internal/modules/cjs/loader:1203:32)
npm error     at Module._load (node:internal/modules/cjs/loader:1019:12)
npm error     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
npm error     at node:internal/main/run_main_module:28:49
npm error
npm error Node.js v18.20.4
npm error
npm error The failure above indicates the primary issue with the native builds which are included for all major platforms. Will now attempt to build the package locally in case this can be resolved by re-compiling.
npm error node:internal/child_process:414
npm error     throw errnoException(err, 'spawn');
npm error     ^
npm error
npm error Error: spawn EINVAL
npm error     at ChildProcess.spawn (node:internal/child_process:414:11)
npm error     at Object.spawn (node:child_process:761:9)
npm error     at build (D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\bin.js:32:8)
npm error     at preinstall (D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\bin.js:41:32)
npm error     at D:\Other\OpenVidu\openvidu-call\openvidu-call-front\node_modules\node-gyp-build-optional-packages\bin.js:14:7
npm error     at ChildProcess.exithandler (node:child_process:430:5)
npm error     at ChildProcess.emit (node:events:517:28)
npm error     at maybeClose (node:internal/child_process:1098:16)
npm error     at ChildProcess._handle.onexit (node:internal/child_process:303:5) {
npm error   errno: -4071,
npm error   code: 'EINVAL',
npm error   syscall: 'spawn'
npm error }
npm error
npm error Node.js v18.20.4
npm error A complete log of this run can be found in: C:\Users\Administrator\AppData\Local\npm-cache\_logs\2024-09-30T01_06_35_209Z-debug-0.log

D:\Other\OpenVidu\openvidu-call\openvidu-call-front>
4

Hi @Qeezy ,

You should be able to work with openvidu call running the following steps:

  1. Clone with
git clone https://github.com/OpenVidu/openvidu-call.git
  1. Run the backend:
cd openvidu-call/backend
npm install 
npm run dev:start
  1. In a new terminal, run the frontend:
cd openvidu-call/frontend
npm install 
npm run dev:start

The application will be available at http://localhost:5080.
Regards