mvschwarz/openrig
1
0 Fork 0
mirror of https://github.com/mvschwarz/openrig.git synced 2026-11-07 05:56:21 -10:00
Code Issues Packages Projects Releases 1 Wiki Activity

docs(contributing): use the npm that comes with Node; a distro npm 9 fails a fresh npm ci (#1731)

Browse Source 
Someone setting up a clone with a separately packaged npm 9, such as Debian's `npm` package (9.2.0), hits a failed `npm ci`: `ENOENT` on `chmod` of `node_modules/@openrig/tui/dist/main.js`.

CONTRIBUTING's setup paragraph now says to use the npm that comes with your Node, which is npm 10 or newer for Node 22 and 24, and shows how to check (`npm --version`). `engines.npm` is unchanged.

Text only: `CONTRIBUTING.md` +3/-1.
This commit is contained in:
Mike Schwarz authored and GitHub committed 2026-10-21 16:59:07 -07:00
1 parent 5f64645e29
commit 82cb85f163
1 file changed
+3 -1
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+3 -1
View File
@@ -42,7 +42,9 @@ repository, and we're happy to link to it.
Node `^22 || ^24`, a working `tmux` and `rsync` are required. macOS includes `rsync`; many Linux
installs don't (`sudo apt-get install rsync` on Debian or Ubuntu). `npm test` and `npm run mirror-skills`
use it. Then:
use it. Use the npm that comes with your Node, which is npm 10 or newer (`npm --version` shows which you
have). A separately packaged npm 9, such as Debian or Ubuntu's `npm` package, fails a fresh `npm ci` with
`ENOENT` on `chmod` of `node_modules/@openrig/tui/dist/main.js`. Then:
```bash
git clone https://github.com/mvschwarz/openrig.git