Frequently Asked Questions Who should we thank for this release?Ī significant amount of work has been done by larixer from SysGears, who crawled deep into the engine with the mission to make the transition to Yarn 2 as easy as possible. Those highlights are only a subset of all the changes and improvements a more detailed changelog can be found here, and the upgrade instructions are available here. Packages are stored in read-only archives.Bundle dependencies aren't supported anymore.Configuration settings have been normalized.Yarn can now be extended through plugins.Peer dependencies now work even through yarn link.Scripts now execute within a normalized shell.Package builds can now be enabled or disabled on a per-package basis.Package builds are now only triggered when absolutely needed.Workspaces can now be declaratively linted and autofixed.A new workflow has been designed to efficiently release workspaces.Local packages can be referenced through the new portal: protocol.Packages can be modified in-place through the patch: protocol.Run commands on all workspaces with yarn workspaces foreach.A safer npx counterpart called yarn dlx to run one-shot tools.
#Barn yarn 2 install#
The output got redesigned for improved readability.Release Overviewĭescribing this release is particularly difficult - it contains core, fundamental changes, shipped together with new features born from our own usage. If you just want to start right now with Yarn 2, check out the Getting Started or Migration guides. If you're interested to know more about what will happen to Yarn 1, keep reading as we detail our plans later down this post: Future Plans. In this post I will explain what this release will mean for our community. Hi everyone! After exactly 365 days of very intensive development, I'm extremely happy to unveil the first stable release of Yarn 2.