Skip to content

Commit 4ca4a26

Browse files
committed
docs(install): add troubleshooting node issues
1 parent ad92287 commit 4ca4a26

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/install.md

+16
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@
1717
- [Docker](#docker)
1818
- [helm](#helm)
1919
- [Cloud Providers](#cloud-providers)
20+
- [Troubleshooting Node Issues](#troubleshooting-node-issues)
2021

2122
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
2223

@@ -228,3 +229,18 @@ See [the chart](../ci/helm-chart).
228229
We maintain one-click apps and install scripts for different cloud providers such as DigitalOcean, Railway, Heroku, Azure, etc. Check out the repository:
229230

230231
[https://github.com/cdr/deploy-code-server](https://github.com/cdr/deploy-code-server)
232+
233+
## Troubleshooting Node Issues
234+
235+
Occassionally, you may run into issues with node.
236+
237+
If you install code-server with `yarn`/`npm` and upgrade your node version, you may need to reinstall code-server to recompile native modules. Sometimes you can get around this by `cd`'ing into the `lib/vscode` directory under code-server and running `npm rebuild` to recompile those native modules.
238+
239+
An example of this might look like:
240+
241+
1. You installed code-server using `brew install code-server`
242+
2. You `cd` into the directory `cd /usr/local/Cellar/code-server/<version>/libexec/lib/vscode/`
243+
3. You recompile native modules by running `npm rebuild`
244+
4. You restart code-server
245+
246+
If you get stuck or need help, post on our [GitHub Discussions page](https://github.com/cdr/code-server/discussions).

0 commit comments

Comments
 (0)