Search Criteria
Package Details: vscodium-electron 1.96.4.25026-1
Package Actions
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: | 8 |
Popularity: | 0.23 |
First Submitted: | 2022-04-10 18:19 (UTC) |
Last Updated: | 2025-01-30 16:05 (UTC) |
Dependencies (11)
- electron32 (electron32-binAUR)
- libsecret
- libx11 (libx11-gitAUR)
- libxkbfile
- ripgrep (ripgrep-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- jq (jaq-binAUR, jq-gitAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- gvfs (gvfs-gitAUR) (optional) – For move to trash functionality
- libdbusmenu-glib (optional) – For KDE global menu
Required by (4)
- vscodium-electron-features
- vscodium-electron-marketplace
- vscodium-features (requires vscodium)
- vscodium-marketplace (requires vscodium)
Latest Comments
1 2 3 4 5 6 7 Next › Last »
Richardn commented on 2025-01-30 16:17 (UTC)
See: https://github.com/microsoft/vscode/issues/238609. TL;DR: By uploading to latest
electron32
, pasting would not work anymore. This is a bug on thevscodium
side present across versions, so downgradingelectron32
is the only fix for now (downgrading this package will not help).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.
electron
version. Actually it for the most of the time depends on older versions, and using newerelectron
actually can break VSCodium.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 ofPKGBUILD
. For myself, I have onlyelectron32
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 cleanchroot
environment. FYI, if you look a few lines above in thePKGBUILD
, you will find me setting up a localnode
environment and installyarn
, so a systemyarn
is not required.Can you try directly
makepkg
-ing withyarn
uninstalled? This may be a problem inyay
I'm afraid.sparr commented on 2025-01-08 13:13 (UTC)
/home/sparr/.cache/yay/vscodium-electron/PKGBUILD: line 115: yarn: command not found
package needs a dependency on yarn
Richardn commented on 2024-10-08 17:00 (UTC) (edited on 2024-10-10 13:55 (UTC) by Richardn)
For those of you waiting for an update: For the latest 1.94 updates, I indeed managed to tweak stuff a bit according to the updated build process, so that this package builds. But after install, calling
codium
will just spawn a vscodium process with nothing showing up on the screen.gdb
sayselectron
is blocking on appoll()
. I am completely loss what is happening. I am asking others for help, and also I may wait for the official code package to update (they also use system electron) and see how they do stuff.--- 2024/10/10 Update ---
Update is online. This helped in updating
vscodium.js
, otherwise as described above, software will simply not start.By the way, although
electron30
is the officially supported version, by my own experienceelectron32
also works fine (andvscode
upstream is already testing withelectron32
). If you want to have a try, just change_electron
toelectron32
and_nodejs
to"20.17.0"
inPKGBUILD
.Richardn commented on 2024-09-10 02:45 (UTC)
Quite a coincidence that just after I pushed the new update, with update to
electron30
, I see your @coxackie's comment xd. Also, thePKGBUILD
is designed in a way so that anyone can change the electron version used (without any guarantees of course). Handy for anyone who only want ONE electron in their system.coxackie commented on 2024-09-09 16:42 (UTC)
I thought
electron30
was used already in 1.92...1 2 3 4 5 6 7 Next › Last »