Arch Linux User Repository

To use custom plugins, customizepkg can be used. In the Github's page, read the "Usage" section and then add and edit the following line (one line per plugin):

addline#prepare#lockfile# git clone PLUGIN_REPO_URL "$srcdir"/$_pkgname/src/userplugins/PLUGIN_NAME

It'll clone the plugins into the right directory and build Vencord including them.

EDIT: Depending on which plugins you're cloning, you might need to prevent the AUR helper from running the check() function, or else the testing phase will fail and prevent from installing it:

With paru: paru -S --nocheck vencord

With yay: yay -S vencord --mflags "--nocheck"

@aria_im yeah, I kinda know it doesn't work since I added the Zen package. Initially I thought it was because the package was installed in /opt/zen-browser-bin instead of /usr/lib/zen-browser, so I reported it. But it never changed.

After a deeper analysis, I think Firefox works because of these lines in the PKGBUILD. zen-browser-bin is probably compiled without these options enabled. zen-browser does have the second line in its PKGBUILD but I haven't tested it yet and it's not a solution to most people since the building time can be very long.

I'll remove the Zen package in the next version, in a few minutes, and if you want to add the extension to Zen you'll need to use firefox-vencord and follow the instructions that will show up after installing it.

Doesn't seem to be working on Zen browser (doesn't show anything under "extensions").

I don't know why, but with every update of vencord/vesktop I still have to edit manually the PKGBUILD file to add the line sed -i '/"packageManager":/d' package.jsonin the prepare() function to avoid the pnpm 10.4.1 error

@apaulsen no idea what might be the issue in your case, I did the same steps as you (with both paru and yay) and it compiles correctly.

I am still seeing the same error that Ranguvar reported. I deleted the cache folder and I tried the steps that dcarmal suggested (using yay --editmenu -S vencord) and still have the error. My pnpm is version 10.6.2-1.

@dcarmal Thank you very much for sharing. The issue is fixed now, @Ranguvar

I've tried to build again and it seems the issue isn't happening anymore, thanks to pnpm's v10.6.0 including a fix.

@Zenith @Ranguvar

In case someone else is having issues with pnpm and node versions, here's my workaround:

first, stablish node.js version with

pnpm env --global use 18.16.0

then, add this line to "prepare()" function in PKGBUILD:

sed -i '/"packageManager":/d' package.json

so it ends up looking like this:

prepare() {
  cd "$srcdir"/$_pkgname
  sed -i '/"packageManager":/d' package.json
  pnpm install --frozen-lockfile
}

Having the same issue as @Ranguvar