Please add yarn(awesome npm alternative)

Will be cool if yarn was integrated to latest node@6 images.
https://yarnpkg.com/

Yarn: A new package manager for JavaScript

It may be a bit premature to decide that yet, but I was thinking about the same yesterday. Given the overwhelmingly positive response to the Yarn release (~9300 GitHub stars in just one day, ~1600 upvotes on HN) this might become a very common request.

I've done a quick test, and adding Yarn to the -slim image (via npm install -g yarn) adds 21.1 MB to the size.

Current official node image sizes:

node    slim    4d8411ec1363    13 days ago 210.3 MB
node    onbuild 275dae106538    13 days ago 653.9 MB

Yep, Yarp adds 10% to size for node:slim but:

disk space is a most cheaper thing
time till run is a most expensive 👟🚀

Agreed that needs to wait some time (a couple of hours 😂) till it became a new standart.

List of most fat packages in yarn. May be some dependencies can be removed. Or bundled with tree-shaking.

6,6M    ./core-js
4,8M    ./lodash
1,7M    ./es5-ext
1,7M    ./node-gyp
928K    ./babel-runtime
548K    ./github

208K    ./bl
244K    ./diff
216K    ./hawk
220K    ./json-schema
244K    ./request
256K    ./sshpk
244K    ./tough-cookie

156K    ./agent-base
168K    ./babel-types
104K    ./dashdash
116K    ./fstream
124K    ./gauge
104K    ./har-validator
112K    ./hoek
100K    ./jodid25519
172K    ./mime-db
168K    ./node-emoji
176K    ./readable-stream
104K    ./tar
184K    ./tweetnacl

It's probably something we could add in the future if there was enough demand for it, but I'm pretty ambivalent about it at this point since it's so new. I'd prefer to keep the images fairly simple, especially the slim variant, since the main point is to use it as a base image and install dependencies etc on top of it.

For installation, I would be more inclined to use the Yarn Debian package repository (under Linux):

https://yarnpkg.com/en/docs/install

That more closely follows the best practices for official images (pgp signed packages):

https://github.com/docker-library/official-images#image-build

For installation, I would be more inclined to use the Yarn Debian package repository (under Linux):

https://yarnpkg.com/en/docs/install

That more closely follows the best practices for official images (pgp signed packages):

https://github.com/docker-library/official-images#image-build

Tried that yesterday. Currently doesn't work on our images, because their packages depend on an installed recent nodejs DEB package (which should probably be relaxed to Recommends or Suggests).

Ugh, ok. Maybe at some point they'll pgp sign the tarball.

It looks like there may be soon a ~ 2 MB bundled release which is CLI-compatible: yarnpkg/yarn#888. If that works, I'm definitely +1 on including it.

Currently doesn't work on our images, because their packages depend on an installed recent nodejs DEB package (which should probably be relaxed to Recommends or Suggests).

This would break the out-of-the-box experience for people that are just getting started. Without Node.js being installed, apt-get install yarn then yarn will show an error about nodejs not being found.

Most people are on Ubuntu 16.04 which has Node.js 4.2.6 in the repo, and the NodeSource repo can be added to get Node 6.

Without Node.js being installed

The absence of a nodejs package does not indicate that Node.js is not installed. There are many popular alternative installation methods, such as nvm, nave, n, make install, binary tarballs, and so on.

@Daniel15

@Daniel15 a Recommends relation would also not break the out-of-the-box experience, as recommended packages are installed by default on both Ubuntu and Debian. But it would allow those who have installed Node in a different way to opt out of the DEB package.

Are we talking about shipping with Yarn? Because that's not a thing in core yet and I'm not sure that is a good idea at this time.

@Fishrock123

@Fishrock123 I don't think any of Docker WG members are suggesting we should add Yarn at this point, but that might change if Yarn becomes a popular request by the masses.

Yes, that's my understanding too: this is just about adding yarn to the docker images.

Any timeline for this?

@andrewmclagan

@andrewmclagan at them moment no, there is a similar discussion over at nodejs/node#9161.

If you guys would tag your releases on here we could fork the repo and use our custom images (including yarn). But since you don't, it's pretty hard to establish a workflow based on your official image (which is sad).

New proposal PR created: #337

The latest version of yarn is now being added via #337

Here's the Docker Hub PR: docker-library/official-images#2703

Looks like yarn was added to all official node images – perfect! README on Docker Hub does not mention yarn so it may be confusing, but the recipes themselves do include it! 🎉 🎉 🎉

Yes, there is a pending PR to update documentation.

@Starefossen

@Starefossen This still seems to be missing from the docs.

I was surprised when I looked at the environment variables for a recent node app to see "YARN_VERSION":"0.21.3". I checked the docs on Docker Hub and there was nothing mentioning Yarn. Eventually I found this issue.

Which PR is supposed to add the docs?

@styfle

@styfle #345 added this to the README of this repository, I'll look into why that has not been propagated onto Docker Hub. Thank you 🙂

Why yarn version is so much outdated? It's still 0.24.6 while latest published is already 0.27.5, which has many minor bug fixes.

Because of a miscommunication in when to update it. Next release will have it updated

@Starefossen

@Starefossen @SimenB Any idea why the readme on Docker Hub is still outdated*?

*Notice no mention of yarn

I don't know how that file is updated...

It requires a separate PR to https://github.com/docker-library/docs

They don't automatically pull in our README.md or docs unfortunately.

Update node README.md

@chorrell

@chorrell Thanks, I submitted a PR in docker-library/docs#964

@romandragan

@romandragan FWIW 8.2.0 will have a updated Yarn installation. We'll update the others when a new version of node is released for them

Navigation Menu

Repository navigation

Please add `yarn`(awesome npm alternative) #243

20 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Please add yarn(awesome npm alternative) #243

Description

Activity

pesho commented on Oct 12, 2016

nodkz commented on Oct 12, 2016

chorrell commented on Oct 12, 2016

pesho commented on Oct 12, 2016

chorrell commented on Oct 12, 2016

pesho commented on Oct 12, 2016

Daniel15 commented on Oct 12, 2016

pesho commented on Oct 12, 2016

pesho commented on Oct 12, 2016

Fishrock123 commented on Oct 17, 2016

Starefossen commented on Oct 17, 2016

chorrell commented on Oct 18, 2016

andrewmclagan commented on Oct 31, 2016

Starefossen commented on Oct 31, 2016

jeremyzahner commented on Nov 2, 2016

20 remaining items

pesho commented on Feb 23, 2017

chorrell commented on Feb 28, 2017

kachkaev commented on Mar 2, 2017

Starefossen commented on Mar 2, 2017

styfle commented on Mar 27, 2017

Starefossen commented on Mar 27, 2017

romandrahan commented on Jul 19, 2017

SimenB commented on Jul 19, 2017

styfle commented on Jul 19, 2017

SimenB commented on Jul 19, 2017

chorrell commented on Jul 19, 2017

styfle commented on Jul 19, 2017

SimenB commented on Jul 20, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Please add `yarn`(awesome npm alternative) #243