cdrci 9cc1033c19 Update Code to 1.146.0 (#8121)
* Stop generating shrinkwraps

npm 12 removes support for shrinkwraps.  Additionally, VS Code has
switched to pnpm and this will make generating the shrinkwraps less
straightforward.

Exact pins in the package.json would not be a sufficient replacement
since that does not cover transitive dependencies.

The recommendation for end user packages installed globally with npm
seems to be to be to bundle dependencies.

One idea would be to build for every platform and bundle them all, but
the whole reason we have the npm package is to support platforms for
which we are not building.  If we build them, we could just add a
regular release for that platform on GitHub.

So instead for each native module we would need to add rebuild commands
in the postinstall.  And ideally remove the current platform builds to
at least try keeping the tarball size down.

I am not sure it is worth the effort for what it feels like fighting
with npm, so this change does not attempt that.

* Remove devDependencies from extensions package.json

Not strictly necessary since we only install production dependencies in
the postinstall, but might as well save some bytes.

* Update Code to 1.146.0

* Support pnpm for post-install

* Get Node version from package.json

lib/vscode/remote/.npmrc no longer exists

* Switch to pnpm

VS Code recently switched to pnpm so various scripts needed to be
updated, and we might as well follow suite with code-server's own
dependencies.

In general this change just swaps out "npm" invocations for "pnpm" plus
any necessary flag changes to match but to call out some less obvious
changes:

1. The extensions directory no longer has a post-install script, so
   there is no need to copy one anymore.
2. When merging the remote package.json, only copy the dependencies
   since that is all we need, to avoid copying in new properties like
   packageManager.
3. Remove unused publish:npm.  It points to a nonexistent file anyway.
4. Remove publish:docker and just call the script directly, to avoid an
   npm/pnpm dependency in a job that really has no need for it.

* Update nfpm maintainer
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2021-12-16 15:30:07 -06:00
2021-01-08 23:03:34 -05:00
2022-03-22 15:07:14 -05:00
2026-10-23 15:06:41 +00:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00
2025-02-12 14:34:05 -09:00
2025-06-25 10:32:43 -08:00
2026-11-20 01:38:16 -09:00
2026-11-20 01:38:16 -09:00

code-server

"GitHub Discussions" "Join us on Slack" Twitter Follow Discord See latest

Run VS Code on any machine anywhere and access it in the browser.

Screenshot Screenshot

Highlights

  • Code on any device with a consistent development environment
  • Use cloud servers to speed up tests, compilations, downloads, and more
  • Preserve battery life when you're on the go; all intensive tasks run on your server

Requirements

See requirements for minimum specs, as well as instructions on how to set up a Google VM on which you can install code-server.

TL;DR: Linux machine with WebSockets enabled, 1 GB RAM, and 2 vCPUs

Getting started

There are four ways to get started:

  1. Using the install script, which automates most of the process. The script uses the system package manager if possible.
  2. Manually installing code-server
  3. Deploy code-server to your team with coder/coder
  4. Using the code-server feature for devcontainers, if you already use devcontainers in your project.

If you use the install script, you can preview what occurs during the install process:

curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run

To install, run:

curl -fsSL https://code-server.dev/install.sh | sh

When done, the install script prints out instructions for running and starting code-server.

Note

To manage code-server for a team on your infrastructure, see: coder/coder

We also have an in-depth setup and configuration guide.

Questions?

See answers to frequently asked questions.

Want to help?

See Contributing for details.

Hiring

Interested in working at Coder? Check out our open positions!

For Teams

We develop coder/coder to help teams to adopt remote development.

S
Description
VS Code in the browser
Readme MIT
149 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 82.7%
Shell 13.5%
HTML 0.9%
CSS 0.7%
HCL 0.7%
Other 1.5%