@Lerm Thanks for looking into it, but in future, please use a pastebin or summarize changes in more compact format.

Here is the patch on top of 2026.6.0-1 to build the proper package (fixing WM class, switch to TS and change from webpack to esbuild):

diff --git a/PKGBUILD b/PKGBUILD
index 40bb28c..004f2a4 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -45,7 +45,7 @@ prepare() (
     > package.tmp && mv package.tmp package.json

   # disable updater
-  sed -E -e '/autoUpdater/d' -i main.js
+  sed -E -e '/autoUpdater/d' -i main.ts
 )

 build() (
@@ -79,8 +79,7 @@ build() (
   rm -rf node_modules/fsevents
   mkdir -p node_modules/fsevents

-  npm exec -c 'webpack --config ./webpack.main.js'
-  npm exec -c 'webpack --config ./webpack.renderer.js'
+  npm exec -c "node ./esbuild.js"
   npm exec -c "electron-builder ${_electron_builder_options[*]}"
 )

@@ -115,7 +114,7 @@ Exec=$_pkgname %U
 Icon=$_pkgname
 Terminal=false
 MimeType=x-scheme-handler/jitsi-meet;
-StartupWMClass=Jitsi Meet
+StartupWMClass=jitsi-meet
 Categories=VideoConference;AudioVideo;Audio;Video;Network;
 END

It seems for 2026.6.0-1 main.js is named main.ts in the source package and thus building it fails.

After renaming main.ts to main.js it started to build only to stop a bit later with a failure about npm version too old: npm notice New minor version of npm available! 11.14.1 -> 11.16.0

It seems that window class has changed in version 2026.5.0 (to 'jitsi-meet'), so now Jitsi windows are not grouped under the launcher icon created by the packge. Following change fixed it for me:

diff --git a/PKGBUILD b/PKGBUILD
index 6632dbe..885ab8f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -115,7 +115,7 @@ Exec=$_pkgname %U
 Icon=$_pkgname
 Terminal=false
 MimeType=x-scheme-handler/jitsi-meet;
-StartupWMClass=Jitsi Meet
+StartupWMClass=jitsi-meet
 Categories=VideoConference;AudioVideo;Audio;Video;Network;
 END

Doesn't work anymore since 2025.9.1 because the app.asar.unpacked directory isn't copied.

thanks. i think it's not a real release because it's only a commit milestone or something (i'm not a coder). but includes update from electron 35 to 37, which would be great to get

hello, 2025.8.1 was just released. can we update the pkgver manually or should we wait for the package update?

This package pins to specific electron version after successful build. Leaving it alone as long as it works.