fix: remote dependencies (#1324)

.github/workflows/insider-linux.yml

@@ -108,7 +108,7 @@ jobs:
         uses: actions/upload-artifact@v3
         with:
           name: remote-dependencies-${{ matrix.vscode_arch }}
-          path: ./vscode/remote/node_modules
+          path: ./remote-dependencies.tar
           retention-days: ${{ needs.check.outputs.SHOULD_DEPLOY == 'yes' && 30 || 1 }}
 
   build:
@@ -175,7 +175,6 @@ jobs:
         uses: actions/download-artifact@v3
         with:
           name: remote-dependencies-${{ matrix.vscode_arch }}
-          path: ./vscode/remote/node_modules
         if: env.SHOULD_BUILD == 'yes' && matrix.vscode_arch == 'x64'
 
       - name: Build

.github/workflows/insider-windows.yml

@@ -114,6 +114,7 @@ jobs:
         shell: bash
     env:
       APP_IDENTIFIER: VSCodium.VSCodium.Insiders
+      ASSETS_REPOSITORY: vscodium-insiders
     if: needs.build.outputs.SHOULD_DEPLOY == 'yes'
 
     steps:

.github/workflows/stable-linux.yml

@@ -102,7 +102,7 @@ jobs:
         uses: actions/upload-artifact@v3
         with:
           name: remote-dependencies-${{ matrix.vscode_arch }}
-          path: ./vscode/remote/node_modules
+          path: ./remote-dependencies.tar
           retention-days: ${{ needs.check.outputs.SHOULD_DEPLOY == 'yes' && 30 || 1 }}
 
   build:
@@ -167,7 +167,6 @@ jobs:
         uses: actions/download-artifact@v3
         with:
           name: remote-dependencies-${{ matrix.vscode_arch }}
-          path: ./vscode/remote/node_modules
         if: env.SHOULD_BUILD == 'yes' && matrix.vscode_arch == 'x64'
 
       - name: Build

.gitignore

@@ -13,3 +13,4 @@ build/linux/appimage/VSCodium
 build/windows/msi/releasedir
 build/windows/msi/Files*.wxs
 build/windows/msi/Files*.wixobj
+remote-dependencies.tar

DOCS.md

@@ -5,7 +5,9 @@
 - [Getting all the Telemetry Out](#disable-telemetry)
   - [Replacements to Microsoft Online Services](#replacement-online-services)
 - [Extensions + Marketplace](#extensions-marketplace)
+  - [How to use the OpenVSX Marketplace](#howto-openvsx-marketplace)
   - [How to use the VS Code Marketplace](#howto-vscode-marketplace)
+  - [How to self host your own VS Code Marketplace](#howto-selfhost-marketplace)
   - [Proprietary Debugging Tools](#proprietary-debugging-tools)
   - [Proprietary Extensions](#proprietary-extensions)
 - [Migrating from Visual Studio Code to VSCodium](#migrating)
@@ -43,7 +45,9 @@ Likewise, while the descriptions for "Extensions: Auto Check Updates" and "Exten
 
 ## <a id="extensions-marketplace"></a>Extensions + Marketplace
 
-The `product.json` file is set up to use [open-vsx.org](https://open-vsx.org/) as extension gallery, which has an [adapter](https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS-Code) to the Marketplace API used by VS Code. Since that is a rather new project, you will likely miss some extensions you know from the VS Code Marketplace. You have the following options to obtain such missing extensions:
+### <a id="howto-openvsx-marketplace"></a>How to use the OpenVSX Marketplace
+
+By default the `product.json` file is set up to use [open-vsx.org](https://open-vsx.org/) as extension gallery, which has an [adapter](https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS-Code) to the Marketplace API used by VS Code. Since that is a rather new project, you will likely miss some extensions you know from the VS Code Marketplace. You have the following options to obtain such missing extensions:
 
 * Ask the extension maintainers to publish to [open-vsx.org](https://open-vsx.org/) in addition to the VS Code Marketplace. The publishing process is documented in the [Open VSX Wiki](https://github.com/eclipse/openvsx/wiki/Publishing-Extensions).
 * Create a pull request to [this repository](https://github.com/open-vsx/publish-extensions) to have the [@open-vsx](https://github.com/open-vsx) service account publish the extensions for you.
@@ -81,6 +85,13 @@ with the content:
 }
 ```
 
+### <a id="howto-selfhost-marketplace"></a>How to self-host your own VS Code Marketplace
+
+Individual developers and enterprise companies in regulated or security-conscious industries can self-host their own VS Code Marketplace using the [code-marketplace](https://coder.com/blog/running-a-private-vs-code-extension-marketplace) open-source project.
+
+> `code-marketplace` is a self-contained go binary that does not have a frontend or any mechanisms for extension authors to add or update extensions in the marketplace. It simply reads extensions from file storage and provides an API for VSCode compatible editors to consume.
+
+
 ### <a id="proprietary-debugging-tools"></a>Proprietary Debugging Tools
 
 The debugger provided with Microsoft's [C# extension](https://github.com/OmniSharp/omnisharp-vscode) as well as the (Windows) debugger provided with their [C++ extension](https://github.com/Microsoft/vscode-cpptools) are very restrictively licensed to only work with the official Visual Studio Code build. See [this comment in the C# extension repo](https://github.com/OmniSharp/omnisharp-vscode/issues/2491#issuecomment-418811364) and [this comment in the C++ extension repo](https://github.com/Microsoft/vscode-cpptools/issues/21#issuecomment-248349017).

build.sh

@@ -2,6 +2,10 @@
 
 set -ex
 
+if [ -f  "./remote-dependencies.tar" ]; then
+  tar -xf ./remote-dependencies.tar ./vscode/remote/node_modules
+fi
+
 . version.sh
 
 if [[ "${SHOULD_BUILD}" == "yes" ]]; then

install_remote_dependencies.sh

@@ -7,3 +7,5 @@ cd vscode || { echo "'vscode' dir not found"; exit 1; }
 yarn --cwd remote --frozen-lockfile --check-files
 
 cd ..
+
+tar -cf remote-dependencies.tar ./vscode/remote/node_modules