Conversation
|
✨ Coder.com for PR #4414 deployed! It will be updated on every commit.
|
jsjoeio
left a comment
There was a problem hiding this comment.
Most of this looks good to me 👍
Biggest question: what's the motivation for changing port from number -> string? And is it considered a breaking change?
jsjoeio
left a comment
There was a problem hiding this comment.
No concerns from me! 👍 Requesting changes since there are conflicts (and I see some todos in the description still). Once those are sorted, lmk and I'll test locally for regressions!
8270613 to
4fd164f
Compare
|
Just fixed the conflicts. But there are ton of TypeScript/testing errors to fix now that |
|
There is a lot to be fixed with this and we need to prioritize getting a release out ASAP so we're going to wait until @TeffenEllis is back to help with this. |
3d8fa51 to
19c9c23
Compare
Our strategy has been to build once and then recompile native modules for individual platforms. It looks like VS Code builds from scratch for each platform. But we can target any platform, grab the pre-packaged folder, then continue with own packaging. In the future we may want to rework to match upstream.
82452bc to
2481711
Compare
The workspace setting seems to be recognized but if so it is having no effect.
506e5e8 to
89cc5a9
Compare
code-asher
left a comment
There was a problem hiding this comment.
We will be knocking out the remaining tasks in separate PRs.
Comments have been addressed, in particular the port is a number again :)
|
I will open new issues and create a milestone for the separate tasks! |



This PR updates code-server to lean more on upstream’s server behaviors.
See code-server-v2 branch on our fork additional changes: https://github.com/cdr/vscode/compare/main...cdr:code-server-v2?expand=1
Breaking changes so far:
TODO:
Moved to separate issue:
typequery param to the web socket connections (used in product) Add type query param to websocket connections #4482To test:
pkill -SIGUSR1 -f code-server)