Arch Linux User Repository

• Completely rewritten patch with correct implementation of transparency for electron window!
• It actually running from compiled binaries! No need for electron dependency!
• No conflicting with official release! You can have installed both!
• Added support for official marketplace!
• Added support for flags configuration file!
• Added support for Wayland!
• Unblocked proprietary features!

How to change window color?

"workbench.colorCustomizations": {
    //Black window color with 75% transparency (#RRGGBBAA)
    "window.background": "#000000BF"
},

..assuming you have a customized theme with all other transparent elements!

Building within clean chroot!

You can build package in completely clean environment without conflicting with any local dependencies (latest nodejs package etc..)!

Execute the following commands inside the package directory:

yes | sudo pacman -S devtools
extra-x86_64-build -c && rm *.log
mapfile -t _pkgs <<< "$(printf '%s\n' code-translucent-*.pkg.tar.zst | sort -Vr)"
sudo pacman -U "${_pkgs[0]}"

..or just run "build-with-chroot.sh" script!

I tried building from TTY and ran into the same issue. Physical memory consumption barely exceeded 4GB when the build crashed. vscodium builds normally.

$ node --max_old_space_size=12288 ./node_modules/gulp/bin/gulp.js --openssl-legacy-provider vscode-linux-x64-min
[15:44:17] Node flags detected: --openssl-legacy-provider
[15:44:17] Respawned to PID: 101058
[15:44:22] Using gulpfile ~/.cache/yay/code-translucent/src/code-translucent/gulpfile.js
[15:44:22] Starting 'vscode-linux-x64-min'...
[15:44:22] Starting clean-out-build ...
[15:44:22] Finished clean-out-build after 5 ms
[15:44:22] Starting build-web-node-paths ...
[15:44:22] Finished build-web-node-paths after 2 ms
[15:44:22] Starting compile-api-proposal-names ...
[15:44:22] Starting compilation api-proposal-names...
[15:44:22] Finished compilation api-proposal-names with 0 errors after 63 ms
[15:44:22] Finished compile-api-proposal-names after 70 ms
[15:44:22] Starting compile-src ...
[15:44:35] [mangler] Done collecting. Classes: 7272. Exported symbols: 8859
[15:44:36] [mangler] Done creating class replacements
[15:44:36] [mangler] Starting prepare rename edits
[15:44:37] Starting compilation...
[15:45:37] 'vscode-linux-x64-min' errored after 1.25 min
[15:45:37] Error [ERR_WORKER_OUT_OF_MEMORY]: Worker terminated due to reaching memory limit: JS heap out of memory
    at new NodeError (node:internal/errors:405:5)
    at [kOnExit] (node:internal/worker:287:26)
    at Worker.<computed>.onexit (node:internal/worker:209:20)
    at Worker.callbackTrampoline (node:internal/async_hooks:130:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> 错误： 在 build() 中发生一个错误。
    正在放弃...

@Similacrest: Yes, but do you have enough free memory? ("free -m" available column). You can try build from TTY without xorg/wayland running ;)

Build is failing both in AUR‌ helper and when I try build-with-chroot.sh. I have 16GB of RAM.

Installing dependencies in test/smoke...
$ yarn --check-files
yarn install v1.22.21
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 1.73s.
Done in 340.73s.
yarn run v1.22.21
$ node --max_old_space_size=8192 ./node_modules/gulp/bin/gulp.js --openssl-legacy-provider vscode-linux-x64-min
[13:25:17] Node flags detected: --openssl-legacy-provider
[13:25:17] Respawned to PID: 8055
[13:25:23] Using gulpfile ~/code-translucent/src/code-translucent/gulpfile.js
[13:25:23] Starting 'vscode-linux-x64-min'...
[13:25:23] Starting clean-out-build ...
[13:25:23] Finished clean-out-build after 3 ms
[13:25:23] Starting build-web-node-paths ...
[13:25:23] Finished build-web-node-paths after 3 ms
[13:25:23] Starting compile-api-proposal-names ...
[13:25:23] Starting compilation api-proposal-names...
[13:25:23] Finished compilation api-proposal-names with 0 errors after 84 ms
[13:25:23] Finished compile-api-proposal-names after 94 ms
[13:25:23] Starting compile-src ...
[13:25:41] [mangler] Done collecting. Classes: 7272. Exported symbols: 8859
[13:25:42] [mangler] Done creating class replacements
[13:25:42] [mangler] Starting prepare rename edits
[13:25:43] Starting compilation...
[13:27:15] 'vscode-linux-x64-min' errored after 1.85 min
[13:27:15] Error [ERR_WORKER_OUT_OF_MEMORY]: Worker terminated due to reaching memory limit: JS heap out of memory
    at new NodeError (node:internal/errors:405:5)
    at [kOnExit] (node:internal/worker:287:26)
    at Worker.<computed>.onexit (node:internal/worker:209:20)
    at Worker.callbackTrampoline (node:internal/async_hooks:130:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/[redacted]/build
Build failed with status code: 255!

@Gursheys: How stuck? Node process corresponding to gulp have no activity? I hope you understand that here the source code is compiling. Can take 15min or far more on low-end hardware!

Gets stuck building/compiling for me, even with clean chroot

It's working good on arch but there is any way to build for windows? I have dual boot and want to have same vscode as on my arch :(

@Rubos: those warnings are expected and normal! Try it now! If not work, please let me know what is output of:

echo "-${DISPLAY:-null}-${XDG_SESSION_TYPE:-null}-${WAYLAND_DISPLAY:-null}-"

@observ33r Sorry for the late reply. Yes I can confirm, launching /opt/code-translucent/bin/code-oss directly fixes the issue for me.

What about Spotify? Spotify is also electron app..

Yeah all other electron apps work ootb. That includes "visual-studio-code-bin"

Interestingly enough, when i execute

/opt/code-translucent/bin/code-oss --ozone-platform=wayland --enable-features=UseOzonePlatform 

I get these warnings with the buggy behavior:

Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

When i start it without these flags i don't get any errors and it just works... (i did set the flags in the .config dir for all electron apps)

Anyways with this workaround it's very usable for me. Thx for the great package