Arch Linux User Repository

As of 2024-09-16, this package is being co-maintained by official vesktop developers, and any packaging decisions they make will not be questioned on my part unless it's something harmful for the users, which is very unlikely to happen. As I see it coming, they will not use the system's electron on this package purposely, if you don't like it, use vesktop-electron, which is also maintained by the same devs.

Thanks!

If anyone is coming here with the same issue Ranguvar has, and doesn't feel like joining the vencord discord:

sudo touch /usr/lib/vencord/package.json

makes vesktop startup again. Hope I could save some time.

@Covkie Sure, joined the server (username carsme_archlinux).

@carsme Can you pop into the Vencord server's Vesktop development channel so we can discuss this a bit? We bundle electron specificly because of its volatile nature and the common breakages between versions.

As a heads-up and to leave room for comments/suggestions - I'm planning to publish vesktop to the official repositories. Packaged using system Electron, so more similar to the vesktop-electron package than this one.

@Ranguvar Hi could you join the vencord server and post in the vesktop - support channel, I believe someone has posted about this before.

As of 1.5.6, I can no longer start this with Vencord 1.11.8 or 1.11.9. Downgrading vesktop to 1.5.5 resolves the issue.

Looks like it's trying to open a package.json which has never existed. I believe the issue is upstream, but I don't use the software enough to warrant creating a GitHub issue.

PPIMAGE env is not defined, current application is not an AppImage
Vesktop v1.5.6
checkForUpdatesAndNotify called, downloadPromise is null
(node:2291466) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, open '/usr/lib/vencord/package.json'
    at async open (node:internal/fs/promises:638:25)
    at async writeFile (node:internal/fs/promises:1212:14)
    at async Promise.all (index 1)
    at async tc (VCDMain:13:849)
    at async Ml (VCDMain:15:4982)
(Use `vesktop --trace-warnings ...` to show where the warning was created)
(node:2291466) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

@ttrrev electron-builder made a breaking change in the config. should be fixed now

Trying to install vesktop via yay but I get an error related to electron-builder. Any hints?

==> Making package: vesktop 1.5.5-4 (Mon Mar 31 01:11:38 2025)
==> Retrieving sources...
  -> Found Vesktop-1.5.5.tar.gz
  -> Found vesktop.desktop
  -> Found vesktop.sh
  -> Found afterPack.js
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
    Vesktop-1.5.5.tar.gz ... Passed
    vesktop.desktop ... Passed
    vesktop.sh ... Passed
    afterPack.js ... Passed
:: (1/1) Parsing SRCINFO: vesktop
==> Making package: vesktop 1.5.5-4 (Mon Mar 31 01:11:40 2025)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found Vesktop-1.5.5.tar.gz
  -> Found vesktop.desktop
  -> Found vesktop.sh
  -> Found afterPack.js
==> Validating source files with sha256sums...
    Vesktop-1.5.5.tar.gz ... Passed
    vesktop.desktop ... Passed
    vesktop.sh ... Passed
    afterPack.js ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting Vesktop-1.5.5.tar.gz with bsdtar
==> Sources are ready.
==> Making package: vesktop 1.5.5-4 (Mon Mar 31 01:11:45 2025)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...

> vesktop@1.5.5 build /home/trev/.cache/yay/vesktop/src/Vesktop-1.5.5
> tsx scripts/build/build.mts

  • electron-builder  version=26.0.12 os=6.13.8-zen1-1-zen
  • loaded configuration  file=package.json ("build" field)
  ⨯ Invalid configuration object. electron-builder 26.0.12 has been initialized using a configuration object that does not match the API schema.
 - configuration.linux should be one of these:
   object { appId?, artifactName?, asar?, asarUnpack?, category?, compression?, cscKeyPassword?, cscLink?, defaultArch?, description?, desktop?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableArgs?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, maintainer?, mimeTypes?, packageCategory?, protocols?, publish?, releaseInfo?, synopsis?, target?, vendor? } | null
  failedTask=build stackTrace=ValidationError: Invalid configuration object. electron-builder 26.0.12 has been initialized using a configuration object that does not match the API schema.
 - configuration.linux should be one of these:
   object { appId?, artifactName?, asar?, asarUnpack?, category?, compression?, cscKeyPassword?, cscLink?, defaultArch?, description?, desktop?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableArgs?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, maintainer?, mimeTypes?, packageCategory?, protocols?, publish?, releaseInfo?, synopsis?, target?, vendor? } | null
    at validate (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/@develar+schema-utils@2.6.5/node_modules/@develar/schema-utils/dist/validate.js:86:11)
    at validateConfiguration (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/app-builder-lib@26.0.12_dmg-builder@26.0.12_electron-builder-squirrel-windows@26.0.12_dmg-bui_5diwh632v6bogr5pndh2ruwtu4/node_modules/app-builder-lib/src/util/config/config.ts:239:3)
    at Packager.validateConfig (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/app-builder-lib@26.0.12_dmg-builder@26.0.12_electron-builder-squirrel-windows@26.0.12_dmg-bui_5diwh632v6bogr5pndh2ruwtu4/node_modules/app-builder-lib/src/packager.ts:384:5)
    at Packager.build (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/app-builder-lib@26.0.12_dmg-builder@26.0.12_electron-builder-squirrel-windows@26.0.12_dmg-bui_5diwh632v6bogr5pndh2ruwtu4/node_modules/app-builder-lib/src/packager.ts:392:5)
    at executeFinally (/home/trev/.cache/pnpm/dlx/ynnkdjpmvut7ntkjttccistpde/195e906ecff-887b6/node_modules/.pnpm/builder-util@26.0.11/node_modules/builder-util/src/promise.ts:12:14)
==> ERROR: A failure occurred in build().

Seems to be a corepack issue with pnpm, see: https://github.com/nodejs/corepack/issues/616, https://github.com/nodejs/corepack/issues/612.

@Edu4rdSHL: Does it work if using makepkg directly?

No, as that is what i was using when I got the same error.

Tried using yay as well, and that didn't work either (I don't know why I tried, but it was nice to see anyway).