OCram85/code-server
Archived
1
0
Fork 0
Code Pull Requests 2 Activity

docs(install): add troubleshooting node issues

Browse Source
This commit is contained in:
Joe Previte 2021-07-01 15:19:16 -07:00
parent ad92287d7e
commit 4ca4a26bec
No known key found for this signature in database
GPG Key ID: 2C91590C6B742C24
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/install.md
View File

@ -17,6 +17,7 @@
- [Docker](#docker)
- [helm](#helm)
- [Cloud Providers](#cloud-providers)
- [Troubleshooting Node Issues](#troubleshooting-node-issues)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
@ -228,3 +229,18 @@ See [the chart](../ci/helm-chart).
We maintain one-click apps and install scripts for different cloud providers such as DigitalOcean, Railway, Heroku, Azure, etc. Check out the repository:
[https://github.com/cdr/deploy-code-server](https://github.com/cdr/deploy-code-server)
## Troubleshooting Node Issues
Occassionally, you may run into issues with node.
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.
An example of this might look like:
1. You installed code-server using `brew install code-server`
2. You `cd` into the directory `cd /usr/local/Cellar/code-server/<version>/libexec/lib/vscode/`
3. You recompile native modules by running `npm rebuild`
4. You restart code-server
If you get stuck or need help, post on our [GitHub Discussions page](https://github.com/cdr/code-server/discussions).