Package Details: vscodium-electron 1.100.13210-1

Git Clone URL: https://aur.archlinux.org/vscodium-electron.git (read-only, click to copy)
Package Base: vscodium-electron
Description: VS Code without MS branding/telemetry/licensing. - System-wide Electron edition
Upstream URL: https://github.com/VSCodium/vscodium
Keywords: code codium electron system vscode vscodium wayland
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: m00nw4tch3r
Maintainer: Richardn
Last Packager: Richardn
Votes: 10
Popularity: 0.70
First Submitted: 2022-04-10 18:19 (UTC)
Last Updated: 2025-05-14 13:58 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

fnrir commented on 2025-05-21 16:12 (UTC)

Unsetting DISPLAY on Wayland breaks running non-Wayland apps in the terminal

oech3 commented on 2025-05-20 07:49 (UTC)

! which $_electron check does nothing since it is installed automatically.

Richardn commented on 2025-05-14 13:12 (UTC)

@Damgaldor is this something peculiar to my package? Based on some initial search I figured it might be an old unfixed issue in vscode, or more accurately, an issue with the sudo-prompt dependency.

I checked the vscodium-bin package on AUR. It also does not look like it will install something under /usr/lib/{$electron}/.

Damgaldor commented on 2025-04-19 20:20 (UTC) (edited on 2025-04-19 20:20 (UTC) by Damgaldor)

This patch/version of Codium breaks saving files with elevated privileges: Unable to save 'file.desktop': Command failed: cd "/usr/share/applications"; "/usr/bin/pkexec" --disable-internal-agent /bin/bash -c "echo SUDOPROMPT; \"/usr/lib/electron34/bin/codium\" --file-write \"/home/damglador/.config/VSCodium/code-elevated-8Fx763Uj\"" /bin/bash: line 1: /usr/lib/electron34/bin/codium: No such file or directory

Richardn commented on 2025-01-30 16:15 (UTC)

@xinayder This is likely caused by certain behaviors of your AUR helper I think. I know some of those would cache the dependency requirements they see from the original repo, so changes you do to PKGBUILD yourself might not be reflected.

xinayder commented on 2025-01-28 19:44 (UTC)

@Richardn that's interesting. I tried editing the PKGBUILD to use the latest electron, and not electron32, and it still falls back to electron32.

Richardn commented on 2025-01-13 15:40 (UTC) (edited on 2025-01-13 15:43 (UTC) by Richardn)

@xinayder No for two reasons.

  1. VSCodium, or to say the VSCode core might not be depending on the latest electron version. Actually it for the most of the time depends on older versions, and using newer electron actually can break VSCodium.
  2. We aim to use system-wide electron here to reduce bloat (in addition to enhanced performance), so users are free to choose whichever electron they already have on their system. The scripts of this package are designed for this purpose, where anyone can change the _electron (and _nodejs) in the beginning of PKGBUILD. For myself, I have only electron32 installed on my system, and both Discord and VSCodium depend on that.

xinayder commented on 2025-01-08 22:56 (UTC) (edited on 2025-01-08 22:56 (UTC) by xinayder)

Shouldn't this package use simply electron and not use a hardcoded version?

Richardn commented on 2025-01-08 17:01 (UTC)

@sparr This is strange, as I don't have yarn installed on my system and everything builds in a clean chroot environment. FYI, if you look a few lines above in the PKGBUILD, you will find me setting up a local node environment and install yarn, so a system yarn is not required.

Can you try directly makepkg-ing with yarn uninstalled? This may be a problem in yay I'm afraid.

1 2 3 4 5 6 7 Next › Last »