Is it me or yarn?

Question

apt works great for me. Rarely a problem and always easy to fix.

conda works great for me. Rarely a problem and always easy to fix.

I can't seem to get yarn to work...ever. Always some strange problem with node version or gyp libraries. Even when I get all of that fixed I get lots of warnings and then errors like

error An unexpected error occurred: "ENOENT: no such file or directory, lstat '/home/balter/.cache/yarn/v4/npm-tar-fs-1.16.3-966a628841da2c4010406a82167cbd5e0c72d509/node_modules/tar-fs/test/fixtures/a/hello.txt'".

Turns out if I run yarn install again there is a different file it can't find. Just for fun, I did

for i in {1..100}; do yarn install; done

Yup it errored on a different file every time, but never did "work."

Is it me, or is yarn just really fragile? If I want to install a package from github and the install instructions use yarn, is there a way around using yarn?

Also, no tag for "yarn"

Answer 1

I had the same problem in WSL one time and fix that using yarn cache clean

Answer 2

I was getting this same frustrating and hard to debug error. The problem in my case seemed to be yarn workspace behaviour caused by different versions of the same dependency in different packages (specifically ava versions 2 and 3). Only once I'd upgraded all occurrences of ava to their latest did I stop getting this error.