Arch Linux User Repository

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?

Describe the bug https://github.com/VSCodium/vscodium/blob/master/docs/index.md) this link is not working after installing vscodium first time in arch linux . when I try to launch vscodium from terminal it gives this error mentioned in below image

Yes, I confirm that this problem is VSCodium-specific - [ ] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

yes, I confirm that the issue/resolution isn't already documented - [ ] I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior: 1. yay -S vscodium (to install vscodium i narch linux) 2.type vscodium in terminal 3. press enter 4. you will see the error message

Expected behavior There was a problem in /usr/share/vscodium/resources/app/product.json I edited this line

"https://open-vsx.org"

as this

"linkProtectionTrustedDomains": [ "https://open-vsx.org" ],

It solved problem and loaded vscodium and now it's works fine

Error message codium node:internal/modules/cjs/loader:1343 throw err; ^

SyntaxError: /usr/share/vscodium/resources/app/product.json: Expected ':' after property name in JSON at position 3747 (line 96 column 2) at parse (<anonymous>) at Module._extensions..json (node:internal/modules/cjs/loader:1340:39) at Module.load (node:internal/modules/cjs/loader:1126:32) at Module._load (node:internal/modules/cjs/loader:967:12) at c._load (node:electron/js2c/node_init:2:13672) at Module.require (node:internal/modules/cjs/loader:1150:19) at require (node:internal/modules/cjs/helpers:119:18) at Object.<anonymous> (/usr/share/vscodium/resources/app/out/cli.js:4:9509) at Module._compile (node:internal/modules/cjs/loader:1271:14) at Module._extensions..js (node:internal/modules/cjs/loader:1326:10) at Module.load (node:internal/modules/cjs/loader:1126:32) at Module._load (node:internal/modules/cjs/loader:967:12) at c._load (node:electron/js2c/node_init:2:13672) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:101:12) at node:internal/main/run_main_module:23:47

@patlefort Thanks for pointing out the python-distutils-extra

@alexmurkoff For the directory issue, the unity-launch flag has been deprecated and have to removed so VSCodium can open directories correctly from any explorer More here: https://github.com/VSCodium/vscodium/pull/1866

The 1.89.1 should fix both issues.

Why force python < 3.12? Installing python-distutils-extra works fine on 3.12. Are there other issues I'm not aware of?

Latest version behaves rather strangely. Latest normally working version is vscodium 1.88.1.24104-1 For more info, look at this forum post: https://bbs.archlinux.org/viewtopic.php?id=295570

TL;DR: Files don't properly open, you have to manually drag n drop each file you need to open or manually open a file with ^O. If you don't care about being able to double-click-open a file from file explorer - ignore this comment.

Missing python-distutils-extra in makedepends.

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