Skip to content

Commit f610adf

Browse files
authored
docs: fix build in readme (#3988)
there is likely a better way to deal with the cmake-js and prebuild dependencies (this is not my world). the build did not work until I installed them. the trezor-build was also required it was yelling about a trezor-glob. otherwise just version bumps
1 parent f91696c commit f610adf

1 file changed

Lines changed: 8 additions & 4 deletions

File tree

‎README.md‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -77,9 +77,9 @@ production.
7777

7878
The current recommended versions for the main tools are:
7979

80-
- Node: 14.16.1
81-
- Npm: 6.4+
82-
- Yarn: 1.12+
80+
- Node: 18.20+
81+
- Npm: 10.8+
82+
- Yarn: 1.22+
8383

8484
To ease node version management, install all top-level tools (node/npm/yarn) using [nvm](https://github.com/nvm-sh/nvm).
8585

@@ -116,6 +116,10 @@ cd decrediton
116116
mkdir bin/
117117
cp $GOPATH/bin/dcr* bin/
118118
yarn
119+
# TODO ? prob these just go in some package file
120+
npm install -g prebuild
121+
npm install -g cmake-js
122+
yarn build-trezor
119123
yarn dev
120124
```
121125

@@ -145,7 +149,7 @@ you're not developing on a daily basis, you can safely ignore this for the
145149
moment.
146150

147151
When starting decrediton in RPC (or "normal") mode, it automatically runs dcrd
148-
in the backgound to gather blockchain data. If you need to constantly restart
152+
in the background to gather blockchain data. If you need to constantly restart
149153
decrediton, loading the node every time may be time consuming.
150154

151155
In that case, it's helpful to run the dcrd node in a separate process and simply

0 commit comments

Comments
 (0)