Alex

There is another more complex example of converted with svgo paths 1.2.2 (this works with rough) > M63.316 8.401l1.091-1.634 1.072-1.612 2.412-3.617A.968.968 0 1066.28.467l-2.584 3.878-1.087 1.63-1.104 1.652c-3.495-1.354-7.392-2.115-11.508-2.115-4.112 0-8.009.76-11.504 2.115l-1.098-1.652-1.087-1.63-2.588-3.88a.97.97 0 00-1.343-.27.968.968...

> Why has there been no movement at all since 2019?! What problem does this solve?

not sure what you want to achieve with that

> There at least few reasons why ~/.yalc may be a bad directory. What reasons?

Ok I've added `--store-folder` flag option. You may check.

> In this scenario, if I call npm install from , it will throw this error: I'm not sure why you get the error for your case. You can make...

> It doesn't need workspaces to be triggered As I said - using workspace is a solution. But I don't get your case, you propose to make some strange contrived...

I think you should simplify the repro case to narrow down the issue. Currently, there some stuff with typescript/rollup/ect. is not related, and some strange manipulation with replacing deps `file:`...

> So I'm kind of stuck. But I think if Yalc used the underlying "npm/yarn pack" command, this wouldn't be an issue. What it should produce using this command?

I believe this could be added but with `yalc pusblish --tgz` probably. So that one on the publishing side chooses the way it should work, and `yalc add` will handle...