Github user xyztdanid4 commented on the issue:
Yes this is the right way to switch to yarn.
Yes we have install yarn locally.
I did not know that we have so much dependency on npm. But for me it was
hard to add new dependencies using npm, cause it was constantly failing. And
yes I would recommend to use yarn, at least for the front end builds. What yarn
does is that reduces the possibility of version mismatch of the dependencies
by importing the dependencies subdependency in the right version. So yes we
have to use yarn commands if we merge this PR.