Arch Linux User Repository

@kronikpillow, this is developer's statement, not mine.
Official builds are made with Electron 22. You can try the official build via webcord-bin to test does it work better for you.

@kronikpillow This isn't just a random comment Hanabishi decided on, if you check upstream this how they specify the compatibility (they allow anywhere from electron 18 to 22).

So if you're having issues with a specific version I would talk with upstream especially for the newer electron versions.

I disagree with @Hanabishi's comment that it's compatible with a wide range of electron versions, on v22 webcord crashes as soon as you open the settings page of webcord ... on v21 it just randomly crashes on it's own, now I'm testing with v20 ... wish there was a note on which version is actually supported so that we would actually use a working version

This isn't the right way to handle this, it's a required dependency so it should be specified using version ranges: depends=('electron>=17' 'electron<23')

I agree, if it would have worked.

Edit: nevermind, looks like the electron packages are structured weirdly and don't provide electron so this has to be the way.

Exactly. If someone has better idea, you are welcome.

Edit: nevermind, looks like the electron packages are structured weirdly and don't provide electron so this has to be the way.

@Hanabishi, Yep, it does by default point to bash, but I have it symlinked to /bin/dash instead since it's a lot closer to the original sh than bash (also quicker). Anyways, nothing wrong with Bash-isms; they make many things a lot easier, but you just gotta be sure you're using the right shell when you use them. :)

@Techi, hmm, strange. In Arch sh points to bash afaik.
Anyway, you are right that it is better to be posix compliant. Check the update.

The little experiment almost worked for me; I had to change the shell in the shebang to /bin/bash since there are some Bash-isms in there (otherwise I use dash as my /bin/sh). After that change though it worked just fine.

Made a little experiment: the package now can run with the whole compatible range of Electron versions.
Compatibility list presented as optional dependencies, you need at least one to be installed.
The latest available version will be choosen automatically at app startup.

This needs electron bumped to 21 as of this commit

@Technetium1 @Hanabishi not really. The less than operator should be threated by Node package managers as exclusive, which means that any Electron version older than 21.0.0 (e.g. 20.3.0) is going to be supported. As 21.0.0 can be the oldest from 21.x.y versions, it should never pick any release from 21.x.y and the users should not upgrade to Electron 21 until I'll prepare WebCord for it.

I've added this range as I still want to support Electron releases downwards 13. For package mangers, the range probably won't change anything: for semver it means that 13 is also being compatible and can be used with this package, but it is not the latest and probably won't be.