Workspaces blog post #580
Workspaces blog post #580
Conversation
Started a blog post about Yarn Workspaces
|
Deploy preview ready! Built with commit 328e501 |
|
The file extension is not |
| }` | ||
| ``` | ||
|
|
||
| An approach that a wrapper like Lerna takes is to run run `yarn install` for each package.json separately and then run `yarn link` for packages that depend on each other. |
|
So the behavior is the same as using --hoist in lerna. Maybe you should mention that. |
|
Is the |
|
|
||
| Do Yarn Workspaces make Lerna obsolete? | ||
|
|
||
| Not at all. |
There was a problem hiding this comment.
This might be a bit misleading. While the current implementation of Yarn Workspaces might not totally replace the functionality of Lerna, the intention is that it will.
Yarn should solve many of the same problems and people should start adapting their tools to work on top of Yarn Workspaces instead of Lerna. I want to eventually deprecate Lerna altogether.
There was a problem hiding this comment.
This could be a different discussion for a different time.
By the time Yarn arrives to feature parity with Lerna the latter may have some opinionated and specific features that Yarn team would not want to copy or maintain.
It will be up to Lerna maintainers to make this decision.
There was a problem hiding this comment.
I designed Lerna so that it intentionally wouldn't have features like that, things that were added should be entirely rethought on top of workspaces
yarn.lock in the root will contain all the resolutions for all workspaces' package.json files. |
incorporated feedback
Started a blog post about Yarn Workspaces.
--- update 31.07.2017
For those waiting for this PR to get merged.
The team decided to hold off the blog post for a couple of weeks to allow some time for bug fixing.
Feedback is still welcome.