Konstantin Raev
Konstantin Raev
Oh wait, your yarn is version 0.17.8, that is very old, can you upgrade to latest? https://yarnpkg.com/en/docs/install
In a way discussed here https://github.com/yarnpkg/rfcs/pull/36
I've seen successful examples of people using folders frontend and backend each with package.json. So far it looks like a somewhat more convenient dependency management in one file is worth...
While yarn has not accepted this feature to categorize dependencies I would use this workaround: Before running `yarn install` modify package.json: 1. Remove dependencies section 2. Rename devDependencies into dependencies...
I'll close the issue because there is a reasonable workaround and simplicity/maintainability of Yarn is a higher priority. It is a community project after all, if there are enough arguments...
Considering that so many people want this I may be incorrect. Let's see how much code is needed to make this change. If it is a few lines of code...
@limonte, here you go
Looks good so far, thanks @eyalzek
I think there are a lot of ways to go around this issue: linking, workspaces, fake offline mirror + tweaking yarn.lock. And this issue is IMHO not common enough to...
Yarn is designed to produce the same results on all computers, it verifies that all dependencies are present and fold/deduplicate the same way. E.g. ``` A -> B -> C@^1.0.1...