Package Details: vscodium 1.89.0.24127-1

Git Clone URL: https://aur.archlinux.org/vscodium.git (read-only, click to copy)
Package Base: vscodium
Description: Free/Libre Open Source Software Binaries of VSCode (git build from latest release).
Upstream URL: https://github.com/VSCodium/vscodium.git
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: cedricroijakkers
Maintainer: cedricroijakkers (daiyam)
Last Packager: cedricroijakkers
Votes: 68
Popularity: 2.12
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2024-05-07 07:09 (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 .. 10 Next › Last »

patlefort commented on 2024-05-06 13:58 (UTC)

Missing python-distutils-extra in makedepends.

jnanar commented on 2024-05-05 09:44 (UTC)

I could build it with the following steps. It's a hack but it worked. I hope the node-gyp upstream team will update the requirements or fix their code to work in the stable release.

git clone https://aur.archlinux.org/vscodium.git
cd vscodium/
python -m venv venv
source venv/bin/activate
pip install setuptools
sudo pacman -U vscodium-1.88.1.24104-1-x86_64.pkg.tar.zst

kreijstal commented on 2024-04-27 14:08 (UTC)

This will no longer build because node-gyp from node18 uses python distutils which are removed in python 3.12. RIP.

sausix commented on 2024-01-18 21:58 (UTC)

Of course it would conflict extra/code. But most people won't install VSCode if they already have VSCodium :-)
Wasn't a request to this package. Just wanted to share my workaround since VSCodium hasn't a dedicated ArchWiki page.
Haven't thought about putting it in ~/.local/bin. Thanks. Applications still may ignore the PATH variable and just look into the known binary folders. Who knows. But I'll test that on UE5.

MithicSpirit commented on 2024-01-18 21:24 (UTC)

@sausix that would make this package conflict with extra/code, which is not necessarily desirable. You could make a separate package that depends on this package but provides and conflicts with code that has that symlink, or just make it manually as you already have (although I would recommend placing the symlink in ~/.local/bin instead).

sausix commented on 2024-01-18 21:20 (UTC)

Create a symlink to get VSCodium being detected by other software. Worked for me on Unreal Engine: ln -s /usr/bin/vscodium /usr/bin/code

komali2 commented on 2023-12-14 08:25 (UTC)

I tried installing and got the following error:

yarn install v1.22.21
warning Skipping preferred cache folder "/.cache/yarn" because it is not writable.
warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-61330".
$ node build/npm/preinstall.js
warning Cannot find a suitable global folder. Tried these: "/usr/local, /.yarn"
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "@microsoft/1ds-core-js > @microsoft/applicationinsights-core-js@2.8.15" has unmet peer dependency "tslib@*".
warning " > gulp-postcss@9.0.0" has unmet peer dependency "postcss@^8.0.0".
warning " > tsec@0.2.7" has unmet peer dependency "@bazel/bazelisk@>=1.7.5".
warning " > tsec@0.2.7" has unmet peer dependency "@bazel/concatjs@>=5.3.0".
[4/4] Building fresh packages...
warning Cannot find a suitable global folder. Tried these: "/usr/local, /.yarn"
error /var/cache/private/pamac/vscodium/src/vscode/node_modules/@parcel/watcher: Command failed.
Exit code: 1
Command: node-gyp-build
Arguments: 
Directory: /var/cache/private/pamac/vscodium/src/vscode/node_modules/@parcel/watcher
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@9.3.1
gyp info using node@18.15.0 | linux | x64
gyp info find Python using Python version 3.11.6 found at "/usr/bin/python3"
gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: ENOENT: no such file or directory, mkdir '/.cache'
gyp ERR! System Linux 6.5.13-1-MANJARO
gyp ERR! command "/var/cache/private/pamac/vscodium/src/.nvm/versions/node/v18.15.0/bin/node" "/var/cache/private/pamac/vscodium/src/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /var/cache/private/pamac/vscodium/src/vscode/node_modules/@parcel/watcher
gyp ERR! node -v v18.15.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! not ok
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: EROFS: read-only file system, open '/.yarnrc'

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 https://github.com/zokugun/vscode-sync-settings/issues/53).

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 https://github.com/microsoft/vscode/issues/197976

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.

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