-
-
Notifications
You must be signed in to change notification settings - Fork 303
Add yarn #65
Comments
As much as I love yarn (it's really cool!) – the aim of this image is to be as small as possible, so I won't add it to the existing image. It's also unlikely that npm can be removed anytime soon, so I won't replace it with yarn either. Best option would be to create your own image with yarn (and no npm perhaps) – or just install it as the first step in your Dockerfile |
I've opened an issue on the Yarn repo to publish it as an Alpine package: yarnpkg/yarn#1326. If someone so inclined helped with that issue, it'd be pretty easy to add |
I tried this both with
Anything missing from your solution @ide ? |
Note that yarn was added to the official node images. nodejs/docker-node#243 I'm not saying it should be added to this image, but just offering an alternative. |
@styfle yeah I noticed that a while back – I thought it would add a lot more weight than that, but it's not too bad. Will definitely consider for 8.x |
Love to see this in node alpine ! |
@mhart do you plan to create a separate image that includes yarn only without npm, or npm & yarn? |
I'll just include yarn with npm in the main image for 8.x – now that Node.js has really grown in size, I think yarn will add only a little overhead, relatively. |
Ok, this will be probably more suitable becase yarn does not fully reflects/implements npm capabilities (for example publishing). When is it planed btw? |
Sometime in the next month I'd say: https://github.com/nodejs/LTS#lts-schedule1 |
BTW consider settings by default |
Included yarn in the latest v8.0.0 image – let me know if anyone has any problems! https://hub.docker.com/r/mhart/alpine-node/ |
Please add yarn!
https://medium.com/@mfornasa/using-yarn-with-docker-c116ad289d56#.a37dpjhmx
The text was updated successfully, but these errors were encountered: