Ilija

Any plans on merging this in? It would be a major improvement over having to embed a 42Mb framework, that then sits in your repo unless you want to deal...

> @cspotcode Yes, as a short-term solution this can definitely be implemented using `bin` hooks to direct at the appropriate download location. I'll also try to take a look this...

cc @ibgreen

Having the same issue. `yarn --cwd foo/bar build` would exit with `Internal Error: ENOENT: no such file or directory, lstat '[REPO_DIR]/foo/bar/foo'`, unclear where the last `foo` is coming from