Arch Linux User Repository

Do NOT report an issues with this package upstream. This package uses system/latest electron. Any issues you have MUST be reproducible in the Flatpak or vesktop packages

@vbmithr This error is a regression caused by nodejs v24.4. Only solution is to downgrade nodejs, or wait until a release containing the patch is made.

==> Lancement de build()…
Lockfile is up to date, resolution step is skipped
Packages: +713
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Downloading app-builder-bin@5.0.0-alpha.10: 72,51 MB/72,51 MB, done
Downloading app-builder-bin@5.0.0-alpha.12: 72,51 MB/72,51 MB, done
Progress: resolved 0, reused 660, downloaded 0, added 710

<--- Last few GCs --->

[1449007:0x7f02fc002000]     3150 ms: Scavenge 397.9 (527.7) -> 397.9 (527.7) MB, pooled: 0 MB, 110.11 / 0.00 ms  (average mu = 0.977, current mu = 0.723) allocation failure; 
[1449007:0x7f02fc002000]     3355 ms: Scavenge 675.5 (805.3) -> 675.5 (805.3) MB, pooled: 0 MB, 40.03 / 0.00 ms  (average mu = 0.977, current mu = 0.723) allocation failure; 

FATAL ERROR: invalid array length Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x5598a1cec8b4 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0x5598a220dd34 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0x5598a220de3b v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x5598a249e42c  [node]
 5: 0x5598a29407fb v8::internal::Runtime_FatalProcessOutOfMemoryInvalidArrayLength(int, unsigned long*, v8::internal::Isolate*) [node]
 6: 0x7f02d7e76636 
^[[27;11;13~
> vesktop@1.5.8 package:dir /home/vb/code/aur/vesktop-electron/src/Vesktop-1.5.8
> pnpm build && electron-builder --dir


> vesktop@1.5.8 build /home/vb/code/aur/vesktop-electron/src/Vesktop-1.5.8
> tsx scripts/build/build.mts

sh: ligne 1: tsx: commande introuvable
 ELIFECYCLE  Command failed.
 ELIFECYCLE  Command failed with exit code 1.
==> ERREUR : Une erreur s’est produite dans build().

looks broken

hicolor icon has no 1024^2 support: https://gitlab.archlinux.org/archlinux/packaging/packages/electron36/-/blob/e36/PKGBUILD

Remove 1024.

Is ^ of "electron": "^35.1.5", of https://raw.githubusercontent.com/Vencord/Vesktop/refs/tags/v1.5.6/package.json means bumping of major ver is also allowed ?

And is editing packaging.json is enough to rebuild .node modules for different electron with pnpm? not .npmrc?

@oech3 I'm not particularly picky about if this uses latest or the major version upstream uses but my idea is if you're using system electron you want latest anyway. lmk if this isn't what you think since you use this package.

How about renaming to vesktop-electron-latest if you don't want to use electronNM?

@ninetailedtori these packages use nodejs corepack pnpm for building. adding pnpm to the dep array is pointless

Please add https://archlinux.org/packages/extra/any/pnpm/ or the AUR bin https://aur.archlinux.org/packages/pnpm-bin to the dependencies.

Do NOT report an issues with this package upstream. This package uses system/latest electron. Any issues you have MUST be reproducible in the Flatpak or vesktop packages