Cd into the addons-frontend repositorynvm useyarn in the same shellyarnRecently I found that the nvm docs had a section for automatically switching node versions if a .nvmrc file existed in the current shell directory for zsh.
After successfully setting that up, I noticed that the version for this project found in .nvmrc is still 6 when yarn requires >= 8.10.
See below for more details:

yarn was unable to install dependencies for this project.
All dependencies would be installed, if necessary.
This should be reproducible on Mac, Windows, and Linux if nvm is installed.
As per the docs found here, the requirements state that users must have Node 8.x which is the current LTS. Let's also update that to say something like Node 8.10!
This comment has a command that would help us update the correct node version inside .nvmrc without having to guess at all 馃榾:
node -v > .nvmrc
It would make sense to checkout the correct version of node (nvm use 8.11.3) then run the above command which should update .nvmrc's contents to be v8.11.3!
.nvmrc
I'd like to help a friend land this as his first ever OSS patch if that's cool 馃槍
I never noticed this .nvmrc file:)
I think we want to keep the same format that we already see:
.nvmrc file. We are not on 10 yet but it seems like we should do that soon!
@willdurand @kumar303 - what do you think?
@rebmullin yes, that's what @SeanPrashad helped me find out that we are on 10 yet , and that's why it was blowing up. I can commit with version '8' in .nvmrc.
Version 8 LTS seems to be the way to go - there are new funky stuff in 10 that will require upgrading and it looks like the team already has plans for Q1 of 2019!
Most helpful comment
I think we want to keep the same format that we already see:
.nvmrcfile.We are not on 10 yet but it seems like we should do that soon!
@willdurand @kumar303 - what do you think?