Package Details: vesktop 1.5.2-5

Git Clone URL: (read-only, click to copy)
Package Base: vesktop
Description: Vesktop gives you the performance of web Discord and the comfort of Discord Desktop
Upstream URL:
Keywords: discord vencord vesktop
Licenses: GPL3
Conflicts: vesktop-bin
Submitter: picokan
Maintainer: Edu4rdSHL
Last Packager: Edu4rdSHL
Votes: 14
Popularity: 4.55
First Submitted: 2024-01-16 08:05 (UTC)
Last Updated: 2024-06-08 21:32 (UTC)

Dependencies (5)

Required by (0)

Sources (4)

Pinned Comments

Edu4rdSHL commented on 2024-04-19 19:11 (UTC) (edited on 2024-04-29 18:33 (UTC) by Edu4rdSHL)

I don't want to be that guy, but:

  • If the package builds using makepkg -s, I don't care if your AUR helper doesn't work, it's a problem with your AUR helper and needs to be fixed there. Here's the build log for the latest version:
  • I can't reproduce the current electron issue with v30, and seems that only a few users are having the issue. So I don't see any reason to downgrade the electron version for everyone. Plus, Athonathonathon put a workaround for it, which seems to be related to the current Chrome breakage on Wayland setups.

The Wayland issue has been fixed from 1.5.1-2 onwards.

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

Edu4rdSHL commented on 2024-06-08 21:32 (UTC)

Thanks, @Fazzi! I forgot to change that after my local testing. Done.

Fazzi commented on 2024-06-08 21:22 (UTC)

Please change patch -Np1 -i "../../fix-pnpm-version-mismatch.patch" to patch -Np1 -i "../fix-pnpm-version-mismatch.patch" to account for different BUILDDIR's in makepkg.conf.

Edu4rdSHL commented on 2024-06-08 20:49 (UTC)

@SomeAspy -5 should fix the issue.

SomeAspy commented on 2024-06-08 20:34 (UTC) (edited on 2024-06-08 20:40 (UTC) by SomeAspy)

Yes, but the problem is you modify the package.json Previously, this was done to resolve the issue of a strict package manager version being needed, however, this has since been fixed in the repository Actually, this has not been merged yet. my bad.

You should be able to revert the sed command on lines 27-31 to resolve the issue once this makes it to stable.

Edu4rdSHL commented on 2024-06-08 20:32 (UTC)

The package builds on a clean chroot environment, if it works, then there's nothing to fix. Use the repo version of pnpm.

SomeAspy commented on 2024-05-28 20:19 (UTC) (edited on 2024-05-28 20:27 (UTC) by SomeAspy)

on systems using the corepack installed version of PNPM, installation will fail.

==> Starting build()...
      throw new UsageError(`No version specified for ${raw} in "packageManager" of ${source}`);

UsageError: No version specified for pnpm@ in "packageManager" of package.json
    at parseSpec (/home/aiden/.nvm/versions/node/v22.2.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23242:13)
    at loadSpec (/home/aiden/.nvm/versions/node/v22.2.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23316:11)
    at async Engine.findProjectSpec (/home/aiden/.nvm/versions/node/v22.2.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23490:22)
    at async Engine.executePackageManagerRequest (/home/aiden/.nvm/versions/node/v22.2.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23542:24)
    at async Object.runMain (/home/aiden/.nvm/versions/node/v22.2.0/lib/node_modules/corepack/dist/lib/corepack.cjs:24235:5) {
  clipanion: { type: 'usage' }

Node.js v22.2.0

Note from Ven:
package issue

vesktop fixed the issue previously:

Edu4rdSHL commented on 2024-05-17 15:40 (UTC)

Now it accepts any pnpm version, @m0tholith. It should work now independent of the pnpm version.

m0tholith commented on 2024-05-17 15:11 (UTC) (edited on 2024-05-17 15:11 (UTC) by m0tholith)

pnpm update causes vesktop to throw an error on compilation. Fixed by installing previous pnpm version

Edu4rdSHL commented on 2024-05-09 03:12 (UTC)

silentnoodle, thanks for reporting. Fixed on

silentnoodle commented on 2024-05-07 18:23 (UTC)

makepkg -si does not work but COREPACK_ENABLE_STRICT=0 makepkg -si does work