code-server-install

A third-party npm distribution channel for the official code-server Linux amd64 Release archive. The archive is split into several npm packages because npm rejects a single package of this size.

This is not the official code-server npm package and is not endorsed by Coder.

Install from an npm mirror

npm install --global [email protected] \
  --registry=https://registry.npmmirror.com

code-server-install assemble "$HOME/code-server-4.134.0-linux-amd64.tar.gz"
mkdir -p "$HOME/.local/opt/code-server-4.134.0"
tar -xzf "$HOME/code-server-4.134.0-linux-amd64.tar.gz" \
  --strip-components=1 \
  -C "$HOME/.local/opt/code-server-4.134.0"
"$HOME/.local/opt/code-server-4.134.0/bin/code-server"

The npm packages contain only archive parts and an assembler. There is no postinstall or preinstall hook, no dependency compilation, and no GitHub request during npm installation. The assembler reads the parts already installed from npm and recreates the original Release tarball.

Supported platform: Linux amd64 (x86_64).

Build the split packages

Use the local archive when the build machine has a proxy or when the archive was downloaded manually:

npm test
npm run build:parts

The build creates:

dist/parts/code-server-install-part-001/
dist/parts/code-server-install-part-002/
...
dist/meta/

Each part is 45 MiB or smaller. The builder preserves the exact byte order and prints the source size. Verify the source archive SHA-256 independently before publishing.

Pack and publish each part first, then publish the meta package:

for part in dist/parts/*; do
  npm publish "$part" --access public --registry=https://registry.npmjs.org/
done
npm publish dist/meta --access public --registry=https://registry.npmjs.org/

Published name@version combinations cannot be overwritten. For a new upstream version, rebuild and publish all part packages and the meta package with the matching version.

See the Chrome section below for the separate Windows installer package.

Chrome Windows offline installer

The same project can split /tmp/ChromeStandaloneSetup64.exe into npm-sized packages. Build it with:

npm run build:chrome

Publish the four parts first, then the small assembler package:

for part in chrome-dist/parts/*; do
  npm publish "$part" --access public --registry=https://registry.npmjs.org/
done
npm publish ./chrome-dist/meta --access public --registry=https://registry.npmjs.org/

On an intranet machine, install from the npm mirror:

npm install --global [email protected] \
  --registry=https://registry.npmmirror.com

chrome-standalone-install assemble "$HOME/ChromeStandaloneSetup64.exe"

Copy the resulting ChromeStandaloneSetup64.exe to a Windows machine and run it manually. The npm package only downloads and combines the installer parts; it does not install Chrome, run an install hook, or access the Internet during installation.

The source installer SHA-256 used for this build is:

ec0de47760a30c53c67ca77842a4acd1b5e6be541bcc2a4476ba303eea4968e1

The code-server Release is distributed under the MIT License. The upstream LICENSE and ThirdPartyNotices.txt files are included in the meta package and must remain with any redistribution. See the upstream project at https://github.com/coder/code-server.