-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support and publish Windows release #1397
Comments
@nhooyr Any updates? Does 3.0 release support Windows? |
There are no self contained windows releases yet. We haven't tested but the npm package might work on windows. |
I was able to install the npm package in windows, but I encounter a few bugs,
Furthermore, running the post install scripts requires Visual Studio and "VC++ 2015.3 v140 toolset for desktop (x86,x64)" to be installed, but since running code-server does not require electron to be built, I think it may be unnecessary. |
@MaxLOh Awesome thanks for looking into it! |
The package is now just
Fixed.
We'll be removing automatic updates soon. See #1532 .
Will mention this in docs, it is required as vscode uses native modules that have to be built. |
- Fix vscode-remote-resource, #1397. - Fix double slash on webview, was causing images not to load. - Fix client-side tar paths.
Asher has fixed the paths, will publish a new release soon. |
We're going to need to test/rewrite any shell scripts that will have to run on Windows. |
Marking this for v3.4.0, couldn't test/get CI going in time for v3.3.0 |
How's the progress going for the windows release? :) |
I only have a couple of minutes, and wanted to dump a couple notes here for y'all I had trouble running code-server in development mode, because of a string smashing bug in
Oddly, this didn't affect it running the npm package version in windows (when I got that hacked about and running). (sorry for the dump, I'll try to come back and put a PR in if I get time) Fixing that, things started working, but I ran into cases where it's failing to read the settings (which means that nothing can be changed)
I went and created a file there, but it still wouldn't go. I haven't gone to look if it's just not liking the slash at the front or what. |
The other problem I had was actually using a terminal window -- it'll start up powershell, but can't interact with the frame at all. Haven't looked into that either. |
I think you're right about the leading slash. I ran this on Windows:
|
If you want to make the path always use forward slashes then I'd still go with
|
Ahhh that makes sense. That's a good point. |
Huh interesting! Sounds like something we will need to look into as
part of this issue.
|
@lavahasif when running the postinstall i keep getting
|
Instead of installing
|
how to install code server on windows |
use npm , it just works like a charm in windows 11 on nodejs 16.20.2 |
yes |
I'm trying to install code-server on my Windows machine using npm, but after following the documentation word for word and reading through every comment in this thread for any insight, I still cannot install code-server on my machine. I used node 16.20.2, avoided using yarn, installed all of the prerequisites for node, added node to my path, and ran my commands through git bash, but nothing seems to be working. Any help is appreciated; my sanity has deteriorated significant since I decided to get involved in this. Attached are the logs of my last installation attempt. |
Unfortunately I have not tried building code-server on Windows so I am not going to be too helpful. There appear to be a few errors, but this one stands out to me: I am not entirely certain where that comes from, but make sure you have all the prerequisites here: https://github.com/microsoft/vscode/wiki/How-to-Contribute |
do you have visual studio 2019 build tools and msvc installed? |
|
Strange. Is it any different with verbose logging? I have seen npm hide installation errors from the post-install script. |
I wonder if we are doing the socket incorrectly on Windows. None of this is currently tested on Windows unfortunately. |
The text was updated successfully, but these errors were encountered: