yarnpkg/yarn
View on GitHub ↗ ★ 41,466 JavaScript
The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
57 mentions on Hacker News by 53 people: 12 stories, 45 comments · first 2016-10-11 · latest 2023-02-28
20082026
-
…https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-... [2] "Yarn's Future - v2 and beyond" https://github.com/yarnpkg/yarn/issues/6953 [3] https://github.com/pnpm/pnpm/blob/main/pkg-manager/core/src/...
comment by rektide · 2023-02-28 · in Benchmarks of JavaScript Package Managers -
…gives 27k results, safe to say discord is severely under-represented in your statistic. [0] https://github.com/yarnpkg/yarn [1] https://github.com/sveltejs/svelte [2] https://sourcegraph.com/search?q=context:global+https://disc...
comment by djrockstar1 · 2021-12-28 · in Please don't use Discord for FOSS projects -
…of weird, complex to reason about stuff that's closer to a bundler than it is to a module manager: https://github.com/yarnpkg/yarn/issues/6953
comment by cfv · 2020-03-17 · in NPM Is Joining GitHub -
>publishConfig https://github.com/yarnpkg/yarn/issues/5310 oops
comment by sascha_sl · 2019-03-12 · in Major bank accidentally published a private package to the public NPM Registry -
▲ 2
Yarn deleted all of my codestory by benvan · 2019-02-28 · 0 comments
-
…the plans to add a pluggable architecture to Yarn 2.0 and support languages other than JavaScript. https://github.com/yarnpkg/yarn/issues/6953
comment by jacobwg · 2019-02-12 · in HHVM 4.0.0 -
▲ 1
Yarn is moving to TypeScriptstory by gejose · 2019-01-28 · 0 comments
-
I hope so, but that feature wasn't there from the start: https://github.com/yarnpkg/yarn/pull/3544 Hopefully they'll be able to re-use much of that work for the Yaml file.
comment by Vinnl · 2019-01-25 · in Yarn's Future – v2 and beyond -
…of it either: documentation; https://yarnpkg.com/lang/en/docs/cli/audit/ original feature issue: https://github.com/yarnpkg/yarn/issues/5808 release comment in that issue: https://github.com/yarnpkg/yarn/issues/5808#issuecomment-441...
comment by coolreader18 · 2019-01-25 · in Yarn's Future – v2 and beyond -
Yarn automatically resolves conflicts in yarn.lock if you run "yarn": https://github.com/yarnpkg/yarn/pull/3544
comment by tlrobinson · 2019-01-24 · in Yarn's Future – v2 and beyond -
▲ 380
Yarn's Future – v2 and beyondstory by arcatek · 2019-01-24 · 232 comments
-
Created an issue over at the Yarn repository: https://github.com/yarnpkg/yarn/issues/6538
comment by KenanSulayman · 2018-10-12 · in NPM and the future of JavaScript -
▲ 5
gitpkg: using git as dependency registrystory by ramasilveyra · 2018-09-17 · 0 comments
-
…version of the current branch, and we have a playground repository to experiment with it. [1] https://github.com/yarnpkg/yarn/pull/6382 [2] https://github.com/yarnpkg/pnp-sample-app
comment by arcatek · 2018-09-13 · in Yarn Plug'n'Play: Getting rid of node_modules -
Here's an issue I've experienced with using upgrade: https://github.com/yarnpkg/yarn/issues/5749
comment by swrobel · 2018-05-29 · in To Yarn and Back to Npm Again -
…to Yarn’s response, also this holiday weekend, to an outage incidentally caused by the NPM team. https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392... Professional, responsive, not afraid of blowback from accepting feedback and…
comment by btown · 2018-05-29 · in NPM proxy users receiving ERR 418 I'm a teapot -
…of an actual CNAME / and use workers to do yarn-specific changes on the edge / (see below). [0]: https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392...
comment by judge2020 · 2018-05-25 · in Yarn registry was down -
…when I hear back." (via [0]) More status on the Github issue [0] than yarn status page [1] [0]: https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392... [1]: https://status.yarnpkg.com/
comment by spdustin · 2018-05-25 · in Yarn registry was down -
Issue is here: https://github.com/yarnpkg/yarn/issues/5885 The problem is that npm just migrated their registry to use CloudFlare. Yarn already used CloudFlare, and had https://registry.yarnpkg.com CNAME'd to https://registry.npmjs.org .…
comment by schneidmaster · 2018-05-25 · in Yarn registry was down -
Reminds me of a recent Yarn problem, overwriting which(1). https://github.com/yarnpkg/yarn/issues/4205
comment by mkj · 2018-02-22 · in Do not use NPM 5.7 -
…not like this. Yarn, by contrast, has everything you would expect of a Facebook-engineered library: https://github.com/yarnpkg/yarn/tree/master/__tests__/util Will be closely evaluating a switch to Yarn for our live apps. This is simply…
comment by btown · 2018-02-22 · in Do not use NPM 5.7 -
…Selenium binaries, and using `yarn install --check-files` instead didn’t help (as suggested here: https://github.com/yarnpkg/yarn/issues/1955#issuecomment-327... ) (I asked this at Medium too)
comment by KajMagnus · 2017-12-17 · in Introducing Turbo: 5x faster than Yarn and NPM, and runs natively in-browser -
Apologies for the issue. There's an issue file on GitHub for this and we are working on a fix: https://github.com/yarnpkg/yarn/issues/4339
comment by BYK · 2017-09-08 · in Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions -
…hand, someone submitted a patch to yarn to improve this behaviour and it was quickly accepted: https://github.com/yarnpkg/yarn/pull/3361 .
comment by brentvatne · 2017-09-07 · in Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions -
…had been approached with more senior developers I think it could have replaced npm entirely. [1] https://github.com/yarnpkg/yarn/issues/2064
comment by brad0 · 2017-09-07 · in Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions -
See https://github.com/yarnpkg/yarn/issues/4320
comment by BYK · 2017-09-07 · in Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions -
▲ 3
Yarn v1.0.0story by htfy96 · 2017-09-07 · 0 comments
-
…This trash article doesn't belong on HN. It doesn't even promote good critical conversation. [1] https://github.com/yarnpkg/yarn/issues/1136#issuecomment-316...
comment by gardnr · 2017-08-23 · in Using Git Wrong -
…cycle you tried to resolve first, and apparently with peerdependencies it sometimes is incorrect ( https://github.com/yarnpkg/yarn/issues/422 ). Any insight as to why it was designed this way? Just the NP-completeness?
comment by zodiac · 2017-07-13 · in How to build a JavaScript package manager -
…usable performance. A problem with yarn was, that it has trouble upgrading all dependencies: https://github.com/yarnpkg/yarn/issues/3492
comment by cel1ne · 2017-07-10 · in Npm v5.1.0 Released -
…fixed 2) yarn upgrade command behavior is sometimes funny, but this is going to be fixed soon: - https://github.com/yarnpkg/yarn/issues/3603 - https://github.com/yarnpkg/rfcs/blob/master/text/0000-upgrad...
comment by leipert · 2017-07-09 · in Npm v5.1.0 Released -
▲ 3
Updated node-emoji just broke yarn for many peoplestory by pbadenski · 2017-07-07 · 0 comments
-
▲ 7
“Oops” Yarn update breaks private npm modulesstory by bradavogel · 2017-06-30 · 0 comments
-
…npm features not being supported. Anyway, here are a couple examples of what I'm talking about: https://github.com/yarnpkg/yarn/issues/3433 https://github.com/yarnpkg/yarn/issues/3507 https://github.com/yarnpkg/yarn/issues/2090 (last one…
comment by ashark · 2017-05-26 · in Npm v5.0.0 released -
▲ 2
Lerna will merge into Yarnstory by gcoguiec · 2016-12-16 · 0 comments
-
▲ 2
Yarn 0.18 Release Notesstory by ggregoire · 2016-12-04 · 0 comments
-
…that significantly improves install times. Really makes me wonder what npm install is doing. [0] https://github.com/yarnpkg/yarn
comment by eatonphil · 2016-11-15 · in Do you really want a single-page application framework? -
…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…
comment by tteller · 2016-11-11 · in Microsoft Kills off ISVs by Foisting Its Own Products That Are No Better -
…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
comment by jakebasile · 2016-10-27 · in MacBook Pro -
Most devs on Github disagree with you: https://github.com/yarnpkg/yarn - 17,271 stars https://github.com/npm/npm - 10,807 stars
comment by terink · 2016-10-25 · in Node.js v7.0.0 -
And 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
comment by po1nter · 2016-10-23 · in NPM v4.0.0 -
…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
comment by octref · 2016-10-23 · in NPM v4.0.0 -
…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
comment by scrollaway · 2016-10-23 · in NPM v4.0.0 -
▲ 24
Yarn 0.16 Release Notesstory by ggregoire · 2016-10-19 · 2 comments
-
anyone knows if yarn has an equivalent of --no-bin-links option? EDIT: guess not according to https://github.com/yarnpkg/yarn/issues/929
comment by kyriakos · 2016-10-18 · in Everything You Wanted to Know About Yarn Package Manager -
▲ 1
Yarn javascript offline package manager is availablestory by ryadIIV · 2016-10-14 · 0 comments
-
Github link: https://github.com/yarnpkg/yarn
comment by dorianm · 2016-10-11 · in Yarn – A new package manager for JavaScript -
…frictionless than any of the alternatives -- exactly like GitHub in the git hosting space). [0]: https://github.com/yarnpkg/yarn/graphs/contributors
comment by pluma · 2016-10-11 · in Yarn – A new package manager for JavaScript -
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...
comment by foxwoods · 2016-10-11 · in Yarn – A new package manager for JavaScript -
…and npm install, with the package having a git url rather than a version in package.json). 0: https://github.com/yarnpkg/yarn/issues/573 1: https://github.com/yarnpkg/yarn/issues/521
comment by pfooti · 2016-10-11 · in Yarn – A new package manager for JavaScript