Alex

What package manager are you using? Config packages that you add are in `.yalc` (eg, `.yalc/*`) folder as workspace packages they should be added Also add them as `--pure` (so...

This PR seems weird, many changes. Won't yarn take care of cleaning up `.bin`, what is the real reason to clean up it?

Soon I believe it will stabilize the release.

We should go to 64 at least, the last number of iChing.

`yalc link` is quite limited in this sense (e.g., when you need to introduce new dependencies), besides it works a bit differently with npm and yarn for example (IIRC yarn...

`yalc add --pure` just copies code to `.yalc`, when using `workspaces` I add `".yalc/*", ".yalc/@*/*"` and yarn creates symlinks itself.

@promethyttrium yes I believe) done

@cdbelyeu You should describe your setup and the issue, you may create a new one.

Yalc puts in and gets packages from the global directory (use `yalc dir` to get witch), so if it is shared in your process...

Seams no way to config this, maybe add the ability to config it via ENV variable?