The architecture is quite simple:
Browser VSC <---wss---> Runner Server <---wss---> Runner Client
This is what will happen when you click "Start Session" in browser:
Note the workflow will run in a forked repo to avoid easy usage limit hitting.
When runner client is online, terminal data will be exchanged via WebSocket. Session ID is required to map correct clients.
Only HTTP requests are supported for now. WebSocket forwarding is not availble.
The VSCode in your browser contains only static assets and it's hosted by GitHub Pages. The deployment is in github-vsc-website.
Powered by the Code - OSS project, and use the tag 1.53.2
for building. Would like not to do any modifications to keep it clean, but here comes to the result (I've tried hard, trust me):
src/vs/code/browser/workbench/workbench.ts
for simple workbench and several html window
related commands.src/vs/code/browser/workbench/one_dark.ts
for One Dark theme.src/vs/workbench/browser/parts/activitybar/activitybarActions.extended.ts
for an extended command to set the index of active side bar. (They just have go prev/next for now, interesting)src/vs/workbench/contrib/welcome/page/browser/vs_code_welcome_page.ts
for customized welcome page.Heads to extensions/github-vsc
, and 2 webpack configs will be shown:
webpack.extension.js
and extension/
for extension itself which runs in a webworker
environment.webpack.web.js
and control-panel/
for the control panel web view which using React / SASS modules.d.ts/
and types/
include shared type definitions.此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。