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.
Pinned Comments
Richardn commented on 2025-01-30 16:17 (UTC)
See: https://github.com/microsoft/vscode/issues/238609. TL;DR: By uploading to latest
electron32
, pasting would not work anymore. This is a bug on thevscodium
side present across versions, so downgradingelectron32
is the only fix for now (downgrading this package will not help).