Currently the installation depends on node v16. So when the frontend installation is done with newer version of node, there will be an error when running yarn. We can see an example of a snapshot of the error message generated:
The current quickest solution is to use nvm and change to any node v16 with npm install <node version> and then npm use <node version>. For the future, a possible improvement is to ensure installation is extended for newer node versions.
Currently the installation depends on node v16. So when the frontend installation is done with newer version of node, there will be an error when running
yarn. We can see an example of a snapshot of the error message generated:The current quickest solution is to use nvm and change to any node v16 with
npm install <node version>and thennpm use <node version>. For the future, a possible improvement is to ensure installation is extended for newer node versions.