BUG: yarn add fail if .lock file with TABs

[JonatasAmaral]

On create-react-app / etc, i've run a conversion of all files' indentation to tabs

Yarn add was failing in one project (while npm add was not), and the only way to use it was to delete the yarn.lock file. Didn't add much packages, so didn't spent time investigating.

Then this got happening on a new one.
I've figured out that the problem is it didn't expect to find a TAB indentation instead of space

[kamronbatman]

Is it necessary to change the indentation to tabs? Usually the file is generated and you leave it alone. The only time it should be modified (in my experience) manually is when you need to do specific package resolution or vuln fixes of nested dependencies.

[JonatasAmaral]

No, it is not. I've done it automatically, then that bug showed up

But now i have to add .yarn files to a exclude config, on each new project. What is king of annoying.
Not to mention (avoiding polemics) that identations should be tabs anyway...