Package Details: vscodium

Git Clone URL: (read-only, click to copy)
Package Base: vscodium
Description: Free/Libre Open Source Software Binaries of VSCode (git build from latest release).
Upstream URL:
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: cedricroijakkers
Maintainer: cedricroijakkers (daiyam)
Last Packager: cedricroijakkers
Votes: 62
Popularity: 1.85
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2023-12-06 09:24 (UTC)

Pinned Comments

cedricroijakkers commented on 2022-09-05 10:41 (UTC)

NOTE: If you are building in a chroot, make sure package systemd-sysvcompat is installed on your system, as this is required for nvm. This cannot be included in the dependencies, since it will break on non-systemd distributions.

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

Richardn commented on 2023-11-25 00:09 (UTC)

Sorry if this appears a bit off-topic: I am now the maintainer of vscodium-electron (which uses system electron) and I have updated it. Check comments and commit logs for details.

daiyam commented on 2023-11-14 19:04 (UTC)

Using the system electron can break some plugins (like

The main objective of VSCodium is to provide an as close as possible version of Visual Studio Code without MS tracking... This version will stay with the included electron

But I could look into the vscodium-electron version. Maybe we could maintain it. Feel free to make any PR, it will be helpful.

By the way, the newer version delay is due to

MithicSpirit commented on 2023-11-11 17:45 (UTC)

While I would personally prefer to use system electron, I think that this package should keep bundling electron unless vscodium officially supports doing it differently. Would be nice to have vscodium-electron be maintained again though, and I'll probably switch over when it is.

Richardn commented on 2023-11-11 17:05 (UTC)

Do you consider making this dependent on the system's electron instead of the electron shipped with vscode?

A discussion (5-years ago) is here talking about the rationale:

Isn't electron meant to be used in this way anyway? You have it on your system once, and everything that wants to use it shares it, rather than having it multiple times.

Clearly this isn't the way it's used in practice, as many projects bundle a copy of electron. It seems like allowing code to use the system electron would be a step in the right direction.

The Archlinux official code package already does that, with this PKGBUILD you can reference. The things to change includes:

  • handling version for the system's electron
  • building native modules for the system's electron before building vscodium
  • replace some strings so that the system's electron is called upon starting vscodium

An alternative AUR package vscodium-electron is designed so, but its maintainer is not responding anyone and the package is seriously out-of-date.

LFdev commented on 2023-11-05 18:18 (UTC)

Thank your for creating and maintaining this package. Please update vscodium-uri-handler.desktop:

$ sudo sed -i "s\/opt/\/usr/share/\\g" /usr/share/applications/vscodium-uri-handler.desktop

Veldora commented on 2023-09-20 09:18 (UTC) (edited on 2023-09-20 09:21 (UTC) by Veldora)

When compiling with makepkg parameters: --cleanbuild --syncdeps --noconfirm --clean and with aurutils I get the following error:

Downloading ripgrep failed: TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
    at new NodeError (node:internal/errors:399:5)
    at new ClientRequest (node:_http_client:189:11)
    at request (node:https:360:10)
    at Object.get (node:https:394:15)
    at /home/user/.cache/aurutils/sync/vscodium/src/vscode/node_modules/@vscode/ripgrep/lib/download.js:141:15
    at new Promise (<anonymous>)
    at get (/home/user/.cache/aurutils/sync/vscodium/src/vscode/node_modules/@vscode/ripgrep/lib/download.js:135:12)
    at getAssetFromGithubApi (/home/user/.cache/aurutils/sync/vscodium/src/vscode/node_modules/@vscode/ripgrep/lib/download.js:190:27)
    at async module.exports (/home/user/.cache/aurutils/sync/vscodium/src/vscode/node_modules/@vscode/ripgrep/lib/download.js:298:9)
    at async main (/home/user/.cache/aurutils/sync/vscodium/src/vscode/node_modules/@vscode/ripgrep/lib/postinstall.js:72:9)

Am I doing something wrong or is there something faulty during the build-process?

daiyam commented on 2023-09-15 07:30 (UTC) (edited on 2023-09-18 07:33 (UTC) by daiyam)

Hi, the 1.82.2 isn't available because VSCode has removed their 1.82.2 tag so the right version can't be downloaded...

Edit: The tag has been re-added and the version has been published

j-c commented on 2023-07-29 08:57 (UTC)

Hi, I tried to install vscodium, but got a couple of errors that some URL's can not be redeclared (like serviceUrl, searchUrl, itemUrl, controlUrl) at starting src/vs/platform/product/common/product.ts.

Does anyone know something about this behaviour?

murchu27 commented on 2023-02-03 14:34 (UTC) (edited on 2023-02-03 15:05 (UTC) by murchu27)

UPDATE: false alarm. I restarted a couple of times (once wasn't enough), and eventually the update worked shrugs

ORIGINAL COMMENT: I'm trying to install the latest build (""), with pamac update -a, but the build fails with the below error:

yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild: Command failed.
Exit code: 1
Command: node install.js
Directory: /var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild
    throw new Error(`Expected ${JSON.stringify("0.15.5")} but got ${JSON.stringify(stdout)}`);

Error: Expected "0.15.5" but got "0.17.5"
    at validateBinaryVersion (/var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild/install.js:93:11)
    at /var/tmp/pamac-build-murchu27/vscodium/src/vscode/build/node_modules/esbuild/install.js:240:5
info Visit for documentation about this command

I notice what it mentions about the esbuild version - my version is indeed "0.17.5". But looking at the dependencies for vscodium, I don't see esbuild mentioned anywhere. Does it really depend on version "0.15.5"? Or is there something else happening here that I'm not understanding?

macxcool commented on 2023-01-07 15:31 (UTC)

and the checksum doesn't match the github file