Great video. I updated to NPM 5.3.0 and am playing around with it. I'm using Ember quite a bit and the latest versions of Ember are encouraging using Yarn instead of NPM. The Ember team has plans to (thank the gods of the machines) dump Bower in favor of Yarn. Note: I don't hate Bower. It's nice for many situations but Ember has two package managers?!? This makes for problematic development especially if you create add-ons.
+Ryan Jentzsch Thanks! I'm not surprised they're supporting yarn. If I remember correctly, Yehuda Katz (one of the creators of Ember) was also one of the creators of yarn. But yes, I'm also glad to see them moving away from bower.
I am using npm 5.x but its still no where close to yarn's speed. yarn killed npm a whie back, now it would take some doing for them to come back to life let alone killing.
I could care less about saving a few seconds while i'm away from my desk getting a coffee while installing / reinstalling my dependencies. For me, the only thing that made Yarn interesting was the Yarn Lock file, as it is much nicer solution than using NPM Shrinkwrap, but now NPM 5's package-lock.json is just as nice to use as Yarn Lock. So now while there might not be any reason to go back to NPM if you're already using Yarn, there's is even less reason to switch to Yarn if you, like most developers, are already using NPM.
I don't think so. I've never heard of that. They do use a dns cname to redirect from registry.yarnpkg.com to the npm registry, but I don't think there's any way to track those requests.
im confused with the new package-lock.json file, so when i want to send my project to my friend, do i send him the package.json file or the package-lock.json file so he can install all the module i have in my project?
It appears you only really need the package.json file. The package-lock.json lists all packages downloaded equally, not just the packages you actually have a dependency on. For instance, say your project has a dependency on request. Your package.json would only list request, but the package-lock.json would list request AND all other packages that request needs. Hope that helps!
Sorry, I might have forgotten something. The package-lock.json file gives you integrity checks on the downloaded dependencies so you can ensure you and your friend are getting the exact same code. But it by itself is not enough.
Correct me if I am wrong but I think if you "npm install" it uses package-lock.json file installing the exact version and on the other hand "npm update" will use package.json to install the latest possible version of the package you want to install provided it doesn't conflict with the other package version.
Yeah, there are plenty of front-end frameworks that are learning from each other. I was more thinking of a year or two ago when a lot of the current standards were still being established. But you're right, Vue is becoming really important these days.
This video isn't about front-end frameworks and only mentioned them to make the point the competition drives improvement and innovation. I've used Angular and Ember and like them both (I use Angular for small web projects and Ember for large ambitious projects). I've heard a lot of good things about React and to be honest I've heard of Vue but I've not heard much from the development community at large about it. When asked what framework to use most developers recommend the big 3: Angular, Ember and React.
> Did npm just kill yarn? Nice clickbait, but no. Yarn is still faster (in some cases twice as fast) than NPM 5.0. Though it did catch up to Yarn enough to dethrone Yarn as the no-brainer choice over NPM. imo, the better looking Yarn CLI UI, and speed advantage could still be enough for many people to stick, or pick Yarn over NPM. But only time will tell. Either way, I fully agree with that we should all be glad existed, since it's probably thanks to this that NPM was forced to innovate and catch up at the rate it did.
Ryan H Lewis its good on my macbook faster downloads and saves space locally, downsides is it makes a shrinkwrap.yml and global installed arn't all worked out yet, i still use 'npm i -g'
Thanks for the performance comparison. I was looking for it.
Hoping Yarn will continue to race NPM as you suggest.
use whatever you want, you probably won't use either in prod where you want to restart your apps on exit
Great video. I updated to NPM 5.3.0 and am playing around with it.
I'm using Ember quite a bit and the latest versions of Ember are encouraging using Yarn instead of NPM. The Ember team has plans to (thank the gods of the machines) dump Bower in favor of Yarn.
Note: I don't hate Bower. It's nice for many situations but Ember has two package managers?!? This makes for problematic development especially if you create add-ons.
+Ryan Jentzsch Thanks! I'm not surprised they're supporting yarn. If I remember correctly, Yehuda Katz (one of the creators of Ember) was also one of the creators of yarn. But yes, I'm also glad to see them moving away from bower.
I am using npm 5.x but its still no where close to yarn's speed. yarn killed npm a whie back, now it would take some doing for them to come back to life let alone killing.
This video was informative and very helpful..
+logic buffer Glad to hear it! Thanks!
I could care less about saving a few seconds while i'm away from my desk getting a coffee while installing / reinstalling my dependencies. For me, the only thing that made Yarn interesting was the Yarn Lock file, as it is much nicer solution than using NPM Shrinkwrap, but now NPM 5's package-lock.json is just as nice to use as Yarn Lock. So now while there might not be any reason to go back to NPM if you're already using Yarn, there's is even less reason to switch to Yarn if you, like most developers, are already using NPM.
+Chunk 1978 Well said!
Does yarn send whatever u use to Facebook 🤔?
I don't think so. I've never heard of that. They do use a dns cname to redirect from registry.yarnpkg.com to the npm registry, but I don't think there's any way to track those requests.
the check is in the post
Speed x2 and it's still understandable
+Brendan Heussler haha, I hope that's a good thing 😀
im confused with the new package-lock.json file, so when i want to send my project to my friend, do i send him the package.json file or the package-lock.json file so he can install all the module i have in my project?
It appears you only really need the package.json file. The package-lock.json lists all packages downloaded equally, not just the packages you actually have a dependency on. For instance, say your project has a dependency on request. Your package.json would only list request, but the package-lock.json would list request AND all other packages that request needs.
Hope that helps!
Sorry, I might have forgotten something. The package-lock.json file gives you integrity checks on the downloaded dependencies so you can ensure you and your friend are getting the exact same code. But it by itself is not enough.
Correct me if I am wrong but I think if you "npm install" it uses package-lock.json file installing the exact version and on the other hand "npm update" will use package.json to install the latest possible version of the package you want to install provided it doesn't conflict with the other package version.
You have missed a huge key player in battle *Vue*
Yeah, there are plenty of front-end frameworks that are learning from each other. I was more thinking of a year or two ago when a lot of the current standards were still being established. But you're right, Vue is becoming really important these days.
Yes and it has surpassed Angular 2 and recently Angular 1 in github stars and its currently competing with react.
This video isn't about front-end frameworks and only mentioned them to make the point the competition drives improvement and innovation.
I've used Angular and Ember and like them both (I use Angular for small web projects and Ember for large ambitious projects). I've heard a lot of good things about React and to be honest I've heard of Vue but I've not heard much from the development community at large about it. When asked what framework to use most developers recommend the big 3: Angular, Ember and React.
yarn is faster than npm
no alias still in npm to install packages with same names but different versions
too little to late now yarn needs it own node.js
The title is wrong, it should be: Did yarn just kill npm?
> Did npm just kill yarn?
Nice clickbait, but no. Yarn is still faster (in some cases twice as fast) than NPM 5.0. Though it did catch up to Yarn enough to dethrone Yarn as the no-brainer choice over NPM. imo, the better looking Yarn CLI UI, and speed advantage could still be enough for many people to stick, or pick Yarn over NPM. But only time will tell.
Either way, I fully agree with that we should all be glad existed, since it's probably thanks to this that NPM was forced to innovate and catch up at the rate it did.
you should try pnpm
I just took a look, it looks pretty awesome! Do you have any experience with it?
Ryan H Lewis its good on my macbook faster downloads and saves space locally, downsides is it makes a shrinkwrap.yml and global installed arn't all worked out yet, i still use 'npm i -g'