Package Details: vscodium-electron 1.96.2.24355-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: 8
Popularity: 0.37
First Submitted: 2022-04-10 18:19 (UTC)
Last Updated: 2024-12-21 04:31 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

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.

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 says electron is blocking on a ppoll(). 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 experience electron32 also works fine (and vscode upstream is already testing with electron32). If you want to have a try, just change _electron to electron32 and _nodejs to "20.17.0" in PKGBUILD.

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, the PKGBUILD 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...

backbord commented on 2024-07-09 14:55 (UTC) (edited on 2024-07-09 14:55 (UTC) by backbord)

@Richardn Thank you very much! Works like a charm!

Another thing I noticed: When I try to open a file in vscodium it will open a new, but empty, instance of vscodium. Found out that removing the --unity-launch in the desktop file fixed it, as it is deprecated. It was also removed in the upstream: https://github.com/VSCodium/vscodium/pull/1866

Richardn commented on 2024-07-03 06:38 (UTC)

@backbord Fix in place. I also put my understanding of the fix as comments in vscodium.js.

By the way, seems like electron release 29.4.3 is officially online now, so we do not need the dirty fix mentioned above with electron29.

backbord commented on 2024-07-02 08:52 (UTC)

Can we get the proposal https://aur.archlinux.org/packages/vscodium-electron#comment-969003 merged? This is the last thing that is required to fix wayland.

Richardn commented on 2024-06-20 02:37 (UTC)

Another day without electron29 update, so you will still be needing the dirty fix mentioned above if you want to build with electron29.

By the way, as a followup to this convo, as now I completely understand the packaging process, I can answer: ripgrep is being depended on because in the usual vscodium package, electron and ripgrep are the only two binary executables present in the compiled files. It is then reasonable for this package to remove both of them and link the system versions of them instead.

1 2 3 4 5 6 Next › Last »