On Thu, Apr 23, 2020 at 10:43 PM Patricia Shanahan <p...@acm.org> wrote: > > On 4/23/2020 7:14 PM, Sam Ruby wrote: > ... > > My bad. Uninstall yarnpkg, and then follow these instructions: > > > > https://classic.yarnpkg.com/en/docs/install#debian-stable > > > >>> sudo snap install --classic code > >>> git clone https://github.com/rubys/whimsy-board-agenda-nodejs > >>> cd whimsy-board-agenda-nodejs > >>> yarn install > >> > >> This is where I got "command not found". > >> > >> pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ echo $PATH > >> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin > >> > >>> yarn dev > >>> code . > > (I am keeping notes and plan to test them on a clean virtual machine > once I get this one up.)
Cool! > Got some warnings from yarn install, and yarn dev failed: > > pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ yarn install > yarn install v1.22.4 > [1/4] Resolving packages... > [2/4] Fetching packages... > info fsevents@2.1.2: The platform "linux" is incompatible with this module. > info "fsevents@2.1.2" is an optional dependency and failed compatibility > check. Excluding it from installation. > info fsevents@1.2.12: The platform "linux" is incompatible with this module. > info "fsevents@1.2.12" is an optional dependency and failed > compatibility check. Excluding it from installation. > [3/4] Linking dependencies... > warning " > @babel/plugin-proposal-class-properties@7.8.3" has unmet > peer dependency "@babel/core@^7.0.0-0". > warning "@babel/plugin-proposal-class-properties > > @babel/helper-create-class-features-plugin@7.8.6" has unmet peer > dependency "@babel/core@^7.0.0". > warning " > @babel/register@7.9.0" has unmet peer dependency > "@babel/core@^7.0.0-0". > warning " > @testing-library/user-event@7.2.1" has unmet peer dependency > "@testing-library/dom@>=5". > warning "react-scripts > @typescript-eslint/eslint-plugin > > tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= > 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= > 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta". > [4/4] Building fresh packages... > [1/5] ⠄ core-js-pure > [2/5] ⠄ dtrace-provider > [3/5] ⠄ nodemon > [1/5] ⡀ core-js-pure > [1/5] ⢀ core-js-pure > [2/5] ⢀ dtrace-provider > [1/5] ⠁ core-js-pure > [-/5] ⠈ waiting... > [-/5] ⠁ waiting... > [-/5] ⠂ waiting... > [2/5] ⠂ dtrace-provider > Done in 60.09s. I'm not concerned about any of those warnings. > pats@Ubuntu2:~/whimsy-board-agenda-nodejs$ yarn dev > yarn run v1.22.4 > $ NODE_ENV=development concurrently --kill-others-on-fail npm:server > npm:client > [server] /bin/sh: 1: npm: not found > [client] /bin/sh: 1: npm: not found > [client] npm run client exited with code 127 > --> Sending SIGTERM to other processes.. > [server] npm run server exited with code 127 > error Command failed with exit code 1. > info Visit https://yarnpkg.com/en/docs/cli/run for documentation about > this command. This is odd. Apparently Ubuntu decided to unbundle npm, requiring you to install it separately: sudo apt install npm The next problem is that they are including an old version of node (10). The current version is 14, and you will need at least 12. There is a nifty tool that can help you update node, which you can install via npm: sudo npm install -g n Once you have installed n, you can use it to get the latest version of node: sudo n latest After you do this, verify that you are running a version of node >= 12: node --version If you get this far, try yarn dev again. - Sam Ruby
