Package Details: vscodium-electron 1.98.2.25072-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: 9
Popularity: 0.37
First Submitted: 2022-04-10 18:19 (UTC)
Last Updated: 2025-03-16 02:24 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

Richardn commented on 2023-07-10 15:04 (UTC) (edited on 2023-10-11 00:44 (UTC) by Richardn)

Is _nodejs="16.17.1" too outdated or something? makepkg yields 404 for https://artifacts.electronjs.org/headers/v16.17.1/node-v16.17.1-headers.tar.gz, thus failing. I switched to 18.16.1 in the PKGBUILD and started making.

The first thing I noticed is that if /usr/lib/$_electron/version does not present, an error will only be generated late in compilation, which is annoying. I suggest defaulting $_electron to none and hinting the user early in the build to set this variable if it is not set properly.

Then, I tried electron19-bin and electron22, both yielded

Error: No checksum found in checksum file for "electron-vXX.X.XX-linux-<arch>..zip"

, failing the build. Is this an upstream bug?

I do not manage a build till now.

--- EDIT ---

I found that if the "current" node.js is not v16.17.1, the build process will try to download v16.17.1 headers from electron.js, and will yield a 404, breaking the build. I nvm use 16.17.1 before makepkg and the making has been progressing. Still, stuck at the checksum issue.

--- EDIT ---

I managed a build with the 2023-08-04 version.

--- EDIT ---

From time to time I randomly encounter the checksum failure problem. A dirty solution is during the build, delete the checksum function call at <package-root>/src/vscode/node_modules/@vscode/gulp-electron/src/download.js:146. I did some prints of the pathnames used, and suspect that the failure is about switching directories when building. I do not have much experience in this, and just noting this down.

Veil commented on 2023-06-06 14:58 (UTC) (edited on 2023-06-06 15:57 (UTC) by Veil)

Is extensions marketplace even work on this package? Infinite loading for me. Nvm marketshare not work with exec electron21 for me. With 22 electron, vscodium don't wanna run with wayland flags. 23-24 electron works, but it load random cpu core to 100% always.

HurricanePootis commented on 2023-04-13 16:48 (UTC)

Vscode upstream does not support electron 22 yet, and is only planning on upgrading to it with version 78 for the mean time. Furthermore, on my system, vscodium.sh launches with wayland properly with the script. What kind of GPU are you using?

ILikesCaviar commented on 2023-04-08 20:09 (UTC) (edited on 2023-04-08 20:10 (UTC) by ILikesCaviar)

I had to make a modification to /usr/bin/codium to get this to work under wayland (mesa driver). I have to use the electron package instead of electron19 and:

--- ELECTRON_RUN_AS_NODE=1 exec electron19 /usr/lib/vscodium/out/cli.js /usr/lib/vscodium/vscodium.js --enable-features=UseOzonePlatform --ozone-platform=wayland "$@"

+++ ELECTRON_RUN_AS_NODE=1 exec electron /usr/lib/vscodium/out/cli.js /usr/lib/vscodium/vscodium.js --ozone-platform=wayland "$@"

HurricanePootis commented on 2023-02-19 18:29 (UTC)

@REmorin, done

REmorin commented on 2023-02-18 15:42 (UTC) (edited on 2023-02-19 11:15 (UTC) by REmorin)

@HurricanePootis, thanks for the info, I'm a bit new to the AUR, so this will be super useful to me.

Btw, please include at least the jq package to the makedepends, as in the vscodium package because the build fails without it.

HurricanePootis commented on 2023-02-16 20:51 (UTC)

@Remorin, Yes I can. Next time, please mark the package out of date so I can see that it is out of date without reading comments

REmorin commented on 2023-02-12 13:11 (UTC)

Hi, could you update the package, pls? It's off by 2 versions.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »