Package Details: vscodium-electron-bin 1.110.11631-1

Git Clone URL: https://aur.archlinux.org/vscodium-electron-bin.git (read-only, click to copy)
Package Base: vscodium-electron-bin
Description: VS Code without MS branding/telemetry/licensing.(Prebuilt and System-wide Electron edition)
Upstream URL: https://vscodium.com/
Keywords: codium editor electron floss ide open-source-licensing vscode
Licenses: MIT
Conflicts: codium, vscodium, vscodium-electron, vscodium-insiders, vscodium-marketplace
Provides: codium, vscodium
Submitter: zxp19821005
Maintainer: zxp19821005
Last Packager: zxp19821005
Votes: 4
Popularity: 0.54
First Submitted: 2024-06-12 07:36 (UTC)
Last Updated: 2026-03-09 02:03 (UTC)

Latest Comments

1 2 Next › Last »

zxp19821005 commented on 2025-12-19 01:29 (UTC)

@landrad221 Thanks for your feedback, fixed it.

landrad221 commented on 2025-12-19 00:26 (UTC) (edited on 2025-12-19 00:28 (UTC) by landrad221)

@zxp19821005 Could you please fix the flags.conf file parsing? I noticed that the $flags variable is not being passed to the Electron command.

zxp19821005 commented on 2025-11-03 02:38 (UTC)

@xinayder The upstream has used electron37 to build it, so I used the electron37 to run it. If you want to use any version of electron, just replace the section _electronversion=37, such as _electronversion=38 or _electronversion=39, then make and install it.

xinayder commented on 2025-10-31 14:31 (UTC) (edited on 2025-10-31 15:13 (UTC) by xinayder)

Could it be possible to remove the hardcoded version dependency for Electron? Assuming one is using the system-wide Electron, then it should only depend on electron itself, and not use a hardcoded version.

I tried changing the version manually on my AUR helper and it still tries to install electron37, even though my electron package points to electron38.

EDIT: one other thing, the binary should be changed to vscodium to keep compatibility with the other packages. this is the only package that provides vscodium-electron binary, all others provide vscodium.

zxp19821005 commented on 2025-10-13 23:00 (UTC)

@derivativeoflog7 Yes, you're right, I've forgot to commit the shell script.Fixed now.

derivativeoflog7 commented on 2025-10-13 22:44 (UTC)

It still appears to be wrong 😅 unless something very weird is going on on my side

sha256sum is giving me 164bbaffe22f4ad43607f44a114528317c4d63592b88e911abadfa962443ac26

zxp19821005 commented on 2025-10-13 20:57 (UTC)

@derivativeoflog7 Thanks for your feedback, fixed it.

derivativeoflog7 commented on 2025-10-13 17:09 (UTC)

Wrong sha256sum for vscodium-electron.sh

zxp19821005 commented on 2025-10-13 02:25 (UTC)

@shoun Thanks for your feedback, I've forgot to update the scripts. Fixed it.

shoun commented on 2025-10-11 20:39 (UTC)

I'm sorry, but your bash bootstrap script is bad. Appending to redeclared _USER_FLAGS is just bad as you're clearing whatever the user could put there before running the app! There's a reason it's done differently in other apps! And also there's bad argv management going on which broke the original bootstrap of /usr/bin/electron and whenever original script tries to apply stuff from electron-flags.conf, it'll always spit out 'bad option'. Please fix this :). Script from https://aur.archlinux.org/cgit/aur.git/tree/vesktop.sh?h=vesktop-bin works perfectly out of the box if one were to reroute the vars and exec order.