Package Details: code-features 1.88.0-1

Git Clone URL: https://aur.archlinux.org/code-features.git (read-only, click to copy)
Package Base: code-features
Description: Unblock some features in Code OSS
Upstream URL: https://github.com/microsoft/vscode
Keywords: vscode
Licenses: unknown
Conflicts: code-features
Provides: code-features
Submitter: sainnhe
Maintainer: sainnhe
Last Packager: sainnhe
Votes: 53
Popularity: 0.35
First Submitted: 2021-04-06 00:46 (UTC)
Last Updated: 2024-04-10 11:28 (UTC)

Required by (1)

Sources (3)

Pinned Comments

sainnhe commented on 2023-08-13 13:31 (UTC)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

jamazi commented on 2022-11-22 15:37 (UTC) (edited on 2022-11-22 15:44 (UTC) by jamazi)

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

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

sainnhe commented on 2022-09-30 04:19 (UTC)

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

prettyvanilla commented on 2022-09-28 18:09 (UTC)

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.

sainnhe commented on 2022-08-24 02:15 (UTC)

@xuiqzy: Thanks! I've added that.

xuiqzy commented on 2022-08-23 22:26 (UTC)

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.

GFdevelop commented on 2022-06-02 17:55 (UTC) (edited on 2022-06-02 17:59 (UTC) by GFdevelop)

@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.

jongeduard commented on 2022-05-27 20:40 (UTC)

@sainnhe You're welcome!

sainnhe commented on 2022-05-05 12:56 (UTC)

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

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

sainnhe commented on 2022-05-05 12:53 (UTC)

@jongeduard: Thanks! It should be fixed now.

GFdevelop commented on 2022-04-20 08:37 (UTC)

ERR command 'liveshare.startFromWelcomeContent' not found: Error: command 'liveshare.startFromWelcomeContent' not found

Package or extension error?

« First ‹ Previous 1 2 3 4 5 Next › Last »