miniblog.

← Back to all posts
Oct 20, 2016 at 21:36
Why I'm Working on Yarn https://yehudakatz.com/2016/10/11/im-excited-to-work-on-yarn-the-new-js-package-manager-2/ (argues, rightly IMO, on the importance of community design over implementation details)
Why I'm Working on Yarn
(This post is about Yarn, a new JS package manager that was announced today [https://code.facebook.com/posts/1840075619545360].) I work with Node and npm packages almost every day, on Tilde's main app, Skylight, or on one of Ember's many packages. Many have remarked upon how fast the npm

Related Posts

Jan 30, 2019 at 04:51
The future of Yarn: https://github.com/yarnpkg/yarn/issues/6953 Breaking up into libraries to enable reuse, and porting to Typescript!
Sep 12, 2017 at 09:49
A nice example of the remarkable modularity in the npm ecosystem: Yarn just split out its lockfile parser https://github.com/yarnpkg/yarn/pull/4114
Sep 11, 2017 at 21:02
This is nifty: yarn will resolve conflicts in lockfiles automatically! https://github.com/yarnpkg/yarn/pull/3544 (novel? I haven't seen other tools do this)
Auto detect and merge lockfile conflicts by sebmck · Pull Request #3544 · yarnpkg/yarn
Auto detect and merge lockfile conflicts by sebmck · Pull Request #3544 · yarnpkg/yarn
Summary Git merge conflicts are common with yarn.lock. This PR allows you to run yarn to automatically merge the two versions of yarn.lock which will run Yarn and regenerate a new lockfile. Test ...