Package Details: visual-studio-code-insiders-bin 1657047632-1

Git Clone URL: (read-only, click to copy)
Package Base: visual-studio-code-insiders-bin
Description: Editor for building and debugging modern web and cloud applications (insiders version)
Upstream URL:
Licenses: custom: commercial
Provides: vscode
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 18
Popularity: 0.75
First Submitted: 2020-11-17 19:53 (UTC)
Last Updated: 2022-07-06 05:55 (UTC)

Pinned Comments

dcelasun commented on 2021-05-29 23:02 (UTC)

This package always installs the latest insiders build so don't flag it as out-of-date, just rebuild and you'll get the latest version.

Latest Comments

greyltc commented on 2022-07-31 17:08 (UTC)

dcelasun, have you considered making a -headless version of this package?

dcelasun commented on 2022-07-06 05:55 (UTC)

@Ashark: done :)

Ashark commented on 2022-07-05 23:22 (UTC)

Can you please add vscode to provides array? See

furai commented on 2022-04-07 14:07 (UTC)

Ok, thanks, it's fixed now.

dcelasun commented on 2022-04-07 12:18 (UTC)

@furai I accidentally pushed checksums when testing out code-flags.conf. Should be fixed now.

furai commented on 2022-04-07 11:14 (UTC) (edited on 2022-04-07 11:26 (UTC) by furai)

It seems that installing this package after recent changes will always fail on shasum checks? Every new update downloaded will have different SHA so we shouldn't be really checking for those?

dcelasun commented on 2022-04-06 21:14 (UTC)

@ZZYSonny fixed, thanks!

ZZYSonny commented on 2022-04-06 20:55 (UTC) (edited on 2022-04-06 20:57 (UTC) by ZZYSonny)


There are a few issues with your approach. In /usr/bin/code-insiders, you forgot to change the /bin/code bit. In .desktop file, you should use the /usr/bin/code-insiders instead of /opt/visual-studio-code-insiders/bin/code-insiders. Otherwise code-flags is not applied.

dcelasun commented on 2022-04-06 19:57 (UTC)

@ZZYSonny done!

ZZYSonny commented on 2022-04-06 19:23 (UTC)

The AUR package visual-studio-code-bin recently added unofficial support for reading flags from ~/.config/electron-flags.conf in the wrapper, which is really useful to enable Ozone Wayland for Visual-studio-code. Any interest implementing the same feature in this package?

alumni commented on 2022-03-18 22:12 (UTC)

Thanks for the update and sorry for flagging (the package manager was not doing a clean build, it was using a cached file instead of downloading the latest version)

etdr commented on 2022-03-14 19:54 (UTC)

Currently this isn't starting for me (or several others) under Wayland, but I doubt there's anything we can do here other than wait for a fix from whoever packaged an incompatible Electron 17 in with VS Code.


MuratOzsoyler commented on 2022-02-10 10:57 (UTC)

@fergal.moran Thank you for replying. I tried to reinstall today and it works.

fergal.moran commented on 2022-02-09 19:03 (UTC)

@MuratOzsoyler it's upstream.

MuratOzsoyler commented on 2022-02-09 10:08 (UTC) (edited on 2022-02-09 10:10 (UTC) by MuratOzsoyler)

visual-studio-code-insiders-bin 1644385586-1 (Wed 09 Feb 2022 12:38:23 PM +03) Causes core dump. Is this related to upstream changes? Or anything wrong with package?

How can I return the previous version if I deleted the relevant package?

dcelasun commented on 2021-12-23 07:03 (UTC)

@chrissnell I couldn't reproduce it in a clean build directory, but I still bumped pkgver for anyone else who might get a 404.

chrissnell commented on 2021-12-23 04:16 (UTC)

I think this package may be out of date but not flagging per instructions. Getting a 404. I updated pkgver to what the Insiders page is distributing and got it to work, but you might want to look at your PKGFILE.

SeriousBug commented on 2021-12-10 23:06 (UTC) (edited on 2021-12-10 23:16 (UTC) by SeriousBug)

I had the same problem where my insiders was stuck on 1.56, which I think was the first version I installed. I was able to update to the latest version once I deleted the cached folder in .cache/paru/clone. I submitted a bug report to paru.

dcelasun commented on 2021-11-02 13:10 (UTC)

@gloomy: Can't reproduce your problem (being stuck in 1.58). When I build & install in a clean directory I get:

Version: 1.62.0-insider
Commit: 4bbec283c36a51cf80f9b77c7a81c140a76a363b
Date: 2021-11-02T08:19:24.222Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
OS: Linux x64 5.14.11-arch1-1

Henry-ZHR commented on 2021-09-22 05:36 (UTC)

It seems that you don't move the bash and zsh completions into the right place

I think this should be helpful

dcelasun commented on 2021-05-29 23:11 (UTC)

No worries, I've stickied a comment for future reference :)

Beomond commented on 2021-05-29 23:10 (UTC)

Sorry, my bad flagging.

dcelasun commented on 2021-05-29 23:02 (UTC)

This package always installs the latest insiders build so don't flag it as out-of-date, just rebuild and you'll get the latest version.

dcelasun commented on 2021-05-01 06:58 (UTC)

You are not using the latest PKGBUILD, the package doesn't use that domain anymore.

noobarchboi commented on 2021-05-01 05:18 (UTC)

I tried updating via makepkg but received this error

ERROR: Failure while downloading

I thought @dcelasun already fixed it? Do I have to manually configure something?

dcelasun commented on 2021-04-20 11:53 (UTC)

Yeah, I just removed the flag.

fishnet37222 commented on 2021-04-20 11:51 (UTC)

Somebody flagged this package as out of date without realizing it automatically pulls in the latest version. Is there a way to remove that flag?

dcelasun commented on 2021-03-24 10:27 (UTC)

@martinus thanks, should be fixed now.

martinus commented on 2021-03-24 10:23 (UTC)

The download from doesn't work any more

ptkdev commented on 2021-01-12 11:46 (UTC)

@dcelasun thanks, with your forced update now work!

dcelasun commented on 2021-01-11 07:31 (UTC)

@ptkdev, are you sure? I just downloaded the package, ran makepkg and pkgver is now 1610342919 which is a build from only a few hours ago.

I'll push an update with that pkgver but it's not necessary. Maybe your AUR helper is caching packages, when in doubt use makepkg manually.

ptkdev commented on 2021-01-11 01:08 (UTC) (edited on 2021-01-11 01:09 (UTC) by ptkdev)

@dcelasun It has stopped updating the package. I tried to rebuild and reinstall but the latest update refers to 2 weeks ago. On windows/mac insiders build is ~14h ago.

dcelasun commented on 2020-11-26 07:52 (UTC)

@hood I don't know, they never gave me a reason. Yes, you should uninstall and reinstall.

hood commented on 2020-11-26 07:50 (UTC)

Why was the previous package nuked? BTW How shall we users proceed at this point? Uninstall then reinstall from this new source?

dcelasun commented on 2020-11-18 18:07 (UTC)

@smittie: I had the explanation for that in the previous package but that was deleted.

The reason is that version number of the insiders build changes several times per day so instead of pushing a new commit for every single build, the package dynamically calculates the latest version at build time. This means that a local build will always have a newer version compared to AUR and that's normal.

smittie commented on 2020-11-18 18:03 (UTC)

Hey, your package seems to be constantly using wrong version numbers. I always have to force installing again...

visual-studio-code-insiders-bin: local (1605704119-1) is newer than AUR (1605592633-1)

Why is that?