Package Details: jitsi-meet-desktop 2023.11.3-1

Git Clone URL: https://aur.archlinux.org/jitsi-meet-desktop.git (read-only, click to copy)
Package Base: jitsi-meet-desktop
Description: Jitsi Meet desktop application
Upstream URL: https://jitsi.org/jitsi-meet/
Keywords: chat IM video
Licenses: Apache
Conflicts: jitsi-meet-electron, jitsi-meet-electron-bin
Replaces: jitsi-meet-electron
Submitter: SamWhited
Maintainer: samsapti
Last Packager: samsapti
Votes: 29
Popularity: 0.009568
First Submitted: 2020-04-10 13:16 (UTC)
Last Updated: 2023-11-25 17:08 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

jsamr commented on 2021-06-07 10:15 (UTC)

Can't make this package with nodejs installed.

v14.17.0 is already installed.
nvm is not compatible with the "npm_config_prefix" environment variable: currently set to "/home/jsamr/.node_modules"
Run `unset npm_config_prefix` to unset it.
Creating default alias: default -> 14 (-> v14.17.0)
nvm is not compatible with the "npm_config_prefix" environment variable: currently set to "/home/jsamr/.node_modules"
Run `unset npm_config_prefix` to unset it.
==> ERROR: A failure occurred in prepare().
    Aborting...
error making: jitsi-meet-desktop

je-vv commented on 2021-05-12 02:10 (UTC)

@lsf, btw, nodejs-webpack-cli provides nodejs-webpack it seems, so if looking into it, perhaps nodejs-webpack-cli becomes a better option, :)

lidesia1733 commented on 2021-04-14 16:31 (UTC) (edited on 2021-04-14 16:32 (UTC) by lidesia1733)

I'm not sure if I did something wrong but this kept failing to compile after installing nvm and nvm-git and the command works for my user.

I edited the PKGBUILD to remove the line, nvm unalias default using and ran the command after compiling.

edit: Clarified what I deleted

lsf commented on 2021-04-11 23:35 (UTC)

That might be an issue considering we're using nvm – but it might be a good idea to try. I'll give it a spin and see how it goes :)

je-vv commented on 2021-04-11 22:49 (UTC)

why aren't nodejs-webpack and/or nodejs-webpack-cli packages optional build time dependencies to avoid downloading them as well? Aren't they needed any longer? They are opt deps for jitsi-meet-electron. I think if system ones could be used, that's way better than downloading them every time, :) Not sure if both needed though, perhaps, just the *-cli package?

je-vv commented on 2021-04-03 19:53 (UTC)

@lsf, it's fine, it's just one line, and perhaps the right one, :) It gets generated at $HOME... Thanks !

lsf commented on 2021-04-03 11:41 (UTC)

Normally it should be enough to just rebuild the package – it probably happened because nodejs got updated in the meantime.

I'll push a new version of jitsi-meet-desktop in a few minutes anyway, so things should work again after you've installed that one :)

@je-vv: np.

where does the .npmrc get generated?

nirnakinho commented on 2021-04-03 11:29 (UTC) (edited on 2021-04-03 11:30 (UTC) by nirnakinho)

Hello,

for a few days, jitsi-meet-desktop fails to start, it gives me the following error message:

App threw an error during load
Error: The module '/tmp/.org.chromium.Chromium.9WLDXQ'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 85. This version of Node.js requires
NODE_MODULE_VERSION 87. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1846)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1138:18)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5:2073)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12684)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/opt/jitsi-meet-desktop/app.asar/node_modules/robotjs/index.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:1078:30)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: The module '/tmp/.org.chromium.Chromium.9WLDXQ'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 85. This version of Node.js requires
NODE_MODULE_VERSION 87. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func [as dlopen] (electron/js2c/asar_bundle.js:5:1846)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1138:18)
    at Object.func [as .node] (electron/js2c/asar_bundle.js:5:2073)
    at Module.load (internal/modules/cjs/loader.js:935:32)
    at Module._load (internal/modules/cjs/loader.js:776:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12684)
    at Module.require (internal/modules/cjs/loader.js:959:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/opt/jitsi-meet-desktop/app.asar/node_modules/robotjs/index.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:1078:30)

I am at loss why there is a conflict between those nodejs module versions, any help is appreciated. Thanks.

Regards,

je-vv commented on 2021-03-31 00:17 (UTC)

@lsf, the export of npm_config_cache, does work, sorry about that. I just noticed the file

% cat .npmrc                                                                                                                                                                                                                       
prefix=/usr

still gets generated though. Which is a minor thing compared to the cache though... Thanks !

DAMO238 commented on 2021-03-29 14:19 (UTC)

@gok's advice worked, even though it didn't install with pacman due to error: target not found: jitsi-meet-desktop, which was solved by manually telling pacman to install the compiled package with sudo pacman -U /path/to/package.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »