Migrate to yarn for packages? about manageiq-ui-service

[chriskacerguis]

@chalettu can you do a little research, and provide your thoughts here?

[chalettu]

Sure, I can take a look. I had been reading about it earlier today but can
explore it to see its possible viability for node package management for
our projects

On Tue, Oct 11, 2016 at 4:09 PM, Chris Kacerguis [email protected]
wrote:

@chalettu https://github.com/chalettu can you do a little research, and
provide your thoughts here?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#245 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOElfHLq4qA8Obm2MbzCXOWp1eD1YIMks5qy_r-gaJpZM4KT_m3
.

Chris Hale

Senior Software Engineer
[email protected]
512-585-7286
https://bluejeans.com/chhale

[jjlangholtz]

I spent a brief amount of time playing with yarn and from what I have seen so far it is an improvement over npm for a few reasons.

1. The yarn.lock file is a much more robust solution than npm-shrinkwrap.json. The former works just like Gemfile.lock, automatically generating a new lock file after running yarn. As long as this lock file is commited in source control, every developer will be using the same dependency versions. Shrinkwrap on the other hand has a few flaws. It must be maintained by hand which is error-prone and puts the onus on the developer updating dependencies to remember updating the shrinkwrap file as well.

2. In very rudimentary benchmarks, yarn is faster and generates less noise during package installations. (For this benchmark I removed the bower install and gulp builds from package.json)

   rm -rf node_modules && npm cache clean && time npm install
   npm install  56.05s user 16.14s system 39% cpu 3:04.96 total
   
   rm -rf node_modules && yarn cache clean  && time yarn
   yarn  40.14s user 17.83s system 39% cpu 2:26.26 total
   

3. The command line interface is much cleaner both in output and in running commands with or without options. When yarn is installing packages it runs in distinct steps that are easy to understand and leave no mystery as to what is going on.

Again, I have only tried using yarn briefly but I am already happy using it over npm. The fact that it shares the same registry for packages as npm and is backed by large companies like Facebook and Google already leads me to believe that it will be adopted rapidly.

[AllenBW]

Yep, looked, sold. Lets do it! Just keep that documentation 🆕 and :fresh: ( 🍇 instead of :fresh: ❓ ) gotta point users to here for instillation and update steps.

A question this raises can we remove requirement for npm? (at least from the readme).

Snap, yarn install saul' ya need to get rolling on this, for sure sold (big fan of things that are easy to use).

[chalettu]

So the thing I think that is left to look at will be to see how we can get travis ci to use yarn as i was reading and travis ci uses npm by default and since yarn is new, I don't believe they have support for it just yet.

[AllenBW]

also this is AWESOME

[chriskacerguis]

Let's move forward with this! Sending to @chalettu for implementation!