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!

Clearly, there's significant disagreement about "properly". (In summary: using bundled Electron goes against much of the spirit and benefits of the AUR outside of explicit -bin packages, and causes some breakage if only minor.)

I'd like to point out that vesktop_electron upgraded to Electron 31, which caused some breakage, and soon after reverted to Electron 30.

I wish this package had done the same during the original breakage, much digital ink would not have been spilled. I don't think it's too late to revert the change, either. I think everyone would be happy, and quickly move on.

picokan, it's just being packaged properly, like any of the packages on the official repos are. There's no need to apologize for something that was done right. Cheers

I want to apologise to all the people that have had problems with the handling of this package. I should've known better than to give away the maintainer role to the first person that asked. If it's any consolation, I haven't had any problems with the vesktop_electron package.

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

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.

@SomeAspy -5 should fix the issue.

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 https://github.com/Vencord/Vesktop/commit/6b948668b9a700aa86ef7c5843d8ab10b668ebf6 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.

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

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

==> Starting build()...
/home/aiden/.nvm/versions/node/v22.2.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23242
      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:

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vesktop#n30
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vesktop-git#n64
package issue

vesktop fixed the issue previously: https://github.com/Vencord/Vesktop/commit/6b948668b9a700aa86ef7c5843d8ab10b668ebf6

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