| 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: | daiyam |
| Votes: | 73 |
| Popularity: | 1.69 |
| First Submitted: | 2021-04-10 15:12 (UTC) |
| Last Updated: | 2024-11-16 02:00 (UTC) |
Latest version (1.95.2) causes crashes for some people when interacting with the file tab of the menu bar: https://github.com/VSCodium/vscodium/issues/2082 https://github.com/VSCodium/vscodium/issues/2115
latest working version is: 1.94.0.24282
Workaround that worked for me: in ~/.config/VSCodium/User/settings.json add the following line: "window.titleBarStyle":_"custom"
Still does not update/install. Had to remove it to update my system.
Just a quick observation. The xz incident has obviously made us more aware of this, but is there a reason why the tar is being downloaded from the release page, and not from the git tag?
I.e. why is https://github.com/VSCodium/vscodium/releases/download/1.91.1.24193/VSCodium-1.91.1.24193-src.tar.gz being used instead of https://github.com/VSCodium/vscodium/archive/refs/tags/1.91.1.24193.tar.gz?
Edit: Raised a GitHub issue - https://github.com/VSCodium/vscodium/issues/1974
Hi there!
Status update: it seems the bundling is still giving an error since the yarn plug n play does not recognize the markdown-itkatex as a dependency.
Hi everyone, hope you are doing ok.
I tried to update vscodium through yay, however it seems is some part of the compilation process is failing as per the Yarn plug n play, stating that two packages "dompurify" and "markdown-it" are not listed as dependencies and hence not resolved.
Please check the error message on detail through the following link: https://pastebin.com/aj0DLC9T
Thank you for your attention
make error https://pastebin.com/gqE4qppC again
It might be possible to use nodejs-lts-iron instead of use of nvm? Isn't it smarter?
diff --git a/PKGBUILD b/PKGBUILD
index d0c589b..50502ba 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -27,7 +27,7 @@ optdepends=(
'libdbusmenu-glib: For KDE global menu'
)
makedepends=(
- 'nvm'
+ 'nodejs-lts-iron'
'gulp'
'yarn'
'jq'
@@ -81,32 +81,6 @@ case "$CARCH" in
esac
build() {
- # Deactivate any pre-loaded nvm, and make sure we use our own in the current source directory
- command -v nvm >/dev/null && nvm deactivate && nvm unload
- export NVM_DIR="${srcdir}/.nvm"
- source /usr/share/nvm/init-nvm.sh || [[ $? != 1 ]]
-
- # Install the correct version of NodeJS (read from .nvmrc)
- nvm install $(cat .nvmrc)
- nvm use
-
- # Check if the correct version of node is being used
- nvmrc_version="$(cat .nvmrc)"
- if [[ "$nvmrc_version" != "v"* ]]
- then
- # Add the v prefix, because it seems to be missing in .nvmrc
- echo "Configured .nvmrc version is [$nvmrc_version], adding the v prefix before checking if it matches with the node command."
- nvmrc_version="v$nvmrc_version"
- fi
-
- # Now check if the version matches exactly, or at least starts with the same prefix
- if [[ "$(node --version)" != "$nvmrc_version"* ]]
- then
- echo "Using the wrong version of NodeJS! Expected ["$nvmrc_version"] but using ["$(node --version)"]."
- exit 1
- fi
- echo "Installed version of node ["$(node --version)"] matches required version ["$nvmrc_version"], continuing."
-
# Remove old build
if [ -d "vscode" ]; then
rm -rf vscode* VSCode*
I am the maintainer of vscodium-electron. I can confirm that yarn and python-distutils-extra are not needed for make, just
npm install --global yarn node-gyp
before building in PKGBUILD.
Motivation is, python-distutils-extra is too much bloat, it references 20+ perl packages. I recommend doing sudo pacman -Rs python-disutils-extra perl-libwww to fully get rid of it.
Responding to below comments, I got confused. node-gyp already resolved python setuptools dependency by vendor in the packaging package, as described here, last year and released node-gyp v10 containing this fix this March (see here).
@blackpanther why is this being reported here? does vscodium directly from upstream not have this issue?
Pinned Comments