Arch Linux User Repository

Upgrading notes for v1.81.1

The code has been refactored in python, upgrading requires manual interventions:

pacman -Rdd code code-features
pacman -S code code-features

Don't reinstall them, uninstall and install these packages instead.

Since the code has been refactored, you can easily modify the code to upgrade to a new version by yourself if I cannot update this package in time. Simply download the latest tarball from code.visualstudio.com and extract them, then run update.py to update patch.json (The usage is documented in update.py), and run makepkg --skipchecksums -i to rebuild and install this package.

Microsoft has introduced new detection method for Pylance extension, now this AUR package cannot bypass the version check of it. Although you can downgrade Pylance to a lower version to continue to use it, but I'd recommend to switch to a FOSS alternative instead (e.g. Pyright) because you'll never know what Microsoft will do in the future. Microsoft sucks :)

The data folder has changed to ~/.vscode because some extensions provided by Microsoft will explicitly use that folder, otherwise they won't work.

You can apparently get pylance to work by renaming .vscode/extensions/ms-python.vscode-pylance-2023.9.10/dist/extension.bundle.js to extension.bundle.js.bak

See https://github.com/VSCodium/vscodium/discussions/1641

After the last update I needed to move all my "~/.config/Code - OSS" folder to "~/.config/Code" and (as stated below) "~/.vscode-oss" to "~/.vscode".

The install script could handle better the version upgrade and not require manual intervention:

pre_upgrade() {
  if [ "$(vercmp "$2" "1.81.1")" -lt 0 ]; then
    sed -i -e 's/^[[:blank:]]*"nameLong":.*/\t"nameLong": "Code - OSS",/' \
      -e 's/^[[:blank:]]*"tunnelApplicationName":.*/\t"tunnelApplicationName": "code-tunnel-oss",/' \
      -e '/^[[:blank:]]*"extensionEnabledApiProposals"/d' \
      -e '/^[[:blank:]]*"extensionSyncedKeys/d' \
      /usr/lib/code/product.json
  else
    /usr/share/code-features/patch.py code-features restore
  fi
}

Upgrading notes for v1.81.1

The code has been refactored in python, upgrading requires manual interventions:

pacman -Rdd code code-features
pacman -S code code-features

Don't reinstall them, uninstall and install these packages instead.

Since the code has been refactored, you can easily modify the code to upgrade to a new version by yourself if I cannot update this package in time. Simply download the latest tarball from code.visualstudio.com and extract them, then run update.py to update patch.json (The usage is documented in update.py), and run makepkg --skipchecksums -i to rebuild and install this package.

Microsoft has introduced new detection method for Pylance extension, now this AUR package cannot bypass the version check of it. Although you can downgrade Pylance to a lower version to continue to use it, but I'd recommend to switch to a FOSS alternative instead (e.g. Pyright) because you'll never know what Microsoft will do in the future. Microsoft sucks :)

The data folder has changed to ~/.vscode because some extensions provided by Microsoft will explicitly use that folder, otherwise they won't work.

With vscode 1.81 for pylance it no longer works.

More specifically, it is the newer version of Pylance that refuses to work on the OSS version, M$ must have introduced new detection mechanism.

Interestingly, the crippled version was only released 23 hours ago as I was writing this. This means that you can install an older version (v2023.8.10) as a temporary workaround.

It can be installed using the Install Another Version option from the Extensions drop-down menu.

@sainhe it would be great if you @DroidFreak32 patch too

@wooptoo:

1. Add extension API proposals to product.json, this will fix some issues in certain extensions (e.g. pylance)

2. Add support for VSCode built-in settings sync.

Excuse the ignorance, what does this package actually do? I've only needed to install this now with the upgrade to vscode v1.74 because of the python extension issue.

Remote-SSH extension doesn't work, however there is a HACKY workaround in product.json:

1) Replace "serverApplicationName": "code-server-oss" With "serverApplicationName": "code-server" This could be added in the patch if you wish to do so, @sainnhe

2) Edit extension's javascript:

Open the Extension's extension.js file, as of this moment it is at: ~/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.92.0/out/extension.js

Find this string:

\n\ttar -xf vscode-server.tar.gz\n\tTAR_EXIT

Replace it with:

\n\ttar -xf vscode-server.tar.gz\n\tsed -i 's/if(this._environmentService.isBuilt)/if(!this._environmentService.isBuilt)/' vscode-server*/out/vs/server/node/server.main.js\n\tTAR_EXIT

This just reverses the condition at remoteExtensionHostAgentServer.ts#L385 so the remote side accepts the OSS Build in "DEV" mode Source