GCgcoguiec·Dec 16, 2016Submission
2 points · Open discussionyarnpkg
yarn
JavaScript2016–2023
yarnpkg / yarn
yarn
The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
53Distinct people
57Mentions
0Explicit recommenders
41.5KGitHub stars
What to know before exploring
What it is
The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- npm/npm · linked in 3 of the same discussions
- yarnpkg/rfcs · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 3:30:57 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year57 dated mentions
Observed mentions: 2016-10-11 15:09:15 UTC to 2023-02-28 20:39:14 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 23 | 5 | 18 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 13 | 3 | 10 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 3 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
23 sourcesFacebook's yarn [0] is a drop-in replacement for 'npm install' that significantly improves install times. Really makes me wonder what npm install is doing.
[0] https://github.com/yarnpkg/yarn
In Do you really want a single-page application framework?AV slows legitimate software that operates on large data sets to the point of it being unusable. Case in point:
https://github.com/yarnpkg/yarn/issues/990
User comment: "MacBookPro takes 17 seconds, my Windows machine takes 122 seconds."
Because of AV - fast on Mac, slow on Windows.
In Microsoft Kills off ISVs by Foisting Its Own Products That Are No BetterI don't know, I see emoji infiltrating my tools more and more. For example, I had to submit a PR to Yarn [1] to add a flag to disable the terrible things. GitHub uses emoji to indicate the type of commit [2].
I hate it.
Edit: I mean GitHub the company, not the product. Atom is maintained by GitHub.
[1]: https://github.com/yarnpkg/yarn/pull/922
[2]: https://github.com/atom/atom/commits/master
In MacBook ProMost devs on Github disagree with you:
https://github.com/yarnpkg/yarn - 17,271 stars
https://github.com/npm/npm - 10,807 stars
In Node.js v7.0.0And if you are using npm & bower in the same project then this other issue is a show stopper https://github.com/yarnpkg/yarn/issues/616
In NPM v4.0.0Yeah I wouldn't use it in production until it becomes more stable. However the team behind it seems to iterate really fast. Look at the issues fixed between public release and 0.16[0], which is only 7 days.
[0]: https://github.com/yarnpkg/yarn/releases/tag/v0.16.0
In NPM v4.0.0I'm super excited to use yarn but, just a heads up, we hit this pretty severe issue when setting it up for our projects: https://github.com/yarnpkg/yarn/issues/761
In NPM v4.0.0anyone knows if yarn has an equivalent of --no-bin-links option?
EDIT: guess not
according to https://github.com/yarnpkg/yarn/issues/929
In Everything You Wanted to Know About Yarn Package ManagerYarn javascript offline package manager is available
1 points · Open discussionGithub link: https://github.com/yarnpkg/yarn
In Yarn – A new package manager for JavaScript> only 2 of those humans work on the CLI
Thanks for clarifying. But that does show that having a company fund two full-time developers to work on the CLI wouldn't have been sufficient. Yarn was mostly built by Seb (403 commits) starting in late January and Konstantin Raev (121 commits) with contributions from several others (<30 commits each). The commit graph[0] actually shows development mostly paused in April and May, putting the total development time closer to half a year.
This most likely includes collaboration with the other people supporting the project (both Seb and Konstantin work for FB) and a lot of architectural planning -- aspects, which likely would have required an even greater investment of time if building on the legacy codebase of the official npm client (not to mention having to negotiate all changes with npm Inc direc
Read the rest
tly).
> wombat is not a tool for managing our other commercial services!
Sorry about the misunderstanding. When wombat came out a lot of people wondered why wombat was a standalone tool when practically every other aspect is part of the npm cli and from what I gathered from npm devs at the time the decision was more of a technical one (different people working on different tools for different things) than a managerial one (different products deserving different tools).
> yarn depends on the npm registry, which depends on npm, Inc making money to keep it running.
Yarn currently uses a downstream mirror of npm as the direct source of truth, with support for private registries being actively worked on to support the private parts of the npm registry and products like npm enterprise or free alternatives like sinopia.
However that is obviously an implementation detail. Decoupling yarn from the npm registry by going through an intermediary allows experimentation (as the npm blog post points out) and ultimately allows avoiding a hard dependency on npm Inc as a company.
If npm Inc were to shut down right now, yarn would still have a read-only mirror. I'm sure Facebook and Google have enough experience solving problems at scale that they could build a public registry alternative if necessary (such as if npm Inc went out of business tomorrow).
I'm not saying yarn will kill npm Inc. But yarn can kill the npm client and replace it with a community-supported alternative (under an open governance model similar to Ember), which in turn makes it a lot easier to fade out the reliance on the public npm registry maintained by npm Inc -- benefiting both the community (by eliminating a single point of commercial failure in the node ecosystem -- exactly like joyent was to the node project) as well as npm Inc (by eliminating a major drag on development resources and cost center).
The only drawback from such a move to npm Inc would be the loss of its privileged position in the ecosystem, the "first mover" advantage of being the place to go if you want private packages (because it's more frictionless than any of the alternatives -- exactly like GitHub in the git hosting space).
[0]: https://github.com/yarnpkg/yarn/graphs/contributors
yarn.lock[0] is similar to composer.lock[1]
[0] https://github.com/yarnpkg/yarn/blob/99dd4504469273332f01ce5...
[1] https://github.com/composer/composer/blob/20ee689bb464edfe7e...
In Yarn – A new package manager for JavaScriptShowing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.