Arch Linux User Repository

About this package

This package installs a hook that will patch product.json every time the code package is updated. The patch basically does the following:

1. Syncs proposed APIs with the latest vscode release. Some extensions don't work in code oss because some specific APIs are not enabled in product.json.
2. Enable built-in settings sync feature.
3. Disable telemetry.
4. Use ~/.vscode and ~/.Code instead of ~/.vscode-oss and ~/.Code OSS.

You might be confused why this package changes the data directory. There are two reasons:

1. Some extensions (e.g. Pylance) require to use the data directory to work.
2. Isolate settings sync data from the OSS version. People may want to install this package because they want to unlock some proprietary extensions, and may have some specific settings that only works with these extensions. Besides, this package will enable built-in sync feature, so isolating the settings may avoid some potential problems such as messing up your synced settings.

If you don't like this behavior, simply create a symlink.

About the maintainance

I'm a vim user, and I rarely use vscode. I created this package simply for fun. And for some reasons, I'm not using Arch Linux as my daily driver anymore.

I'll continue to maintain this package for a while until my old Arch Linux machine retires. If you want to become a maintainer of this package, feel free to contact me (i@sainnhe.dev).

Updating the package is very simple, you just need to run update.py in the root of this repository. The script will automatically update patch.json which contains the patch data.

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

pylance will try to lookup files in ~/.vscode/extensions directory then it will fail, solution :

ln -s ~/.vscode-oss ~/.vscode

@prettyvanilla: This package needs to be updated, but I don't have time recently. Anyone wants to be a maintainer?

Looking into the Developer Tools Console I noticed that there are currently mismatches between what some extensions want and what API proposals are currently enabled/patched in. The following seem to be missing:

"ms-vscode.js-debug" (and I presume "ms-vscode.js-debug-nightly" consequently as well) misses the "tunnels" API, and "ms-vscode.remote-repositories" misses "contribShareMenu" and "editSessionIdentityProvider". Unless there are reasons not to enable these it would be great if you could add them.

@xuiqzy: Thanks! I've added that.

Should maybe optionally depend on icu69 for liveshare to work with the code package, since it is only usable with this package as a feature not available in the code build normally.

@sainnhe the real issue it's here https://github.com/MicrosoftDocs/live-share/issues/4669 and install the icu69 aur package it's the solution.

I have tried icu70 and work, it don't replace the icu package and you can have installed icu and icu70 together.

@sainnhe You're welcome!

@GFdevelop: I found the exact issue on github, looks like a packaging issue of community/code.

https://github.com/MicrosoftDocs/live-share/issues/4229