To Yarn and Back to Npm Again

#1

Post by wearhere » Tue, May 29, 2018, 6:11 PM UTC

To Yarn and Back to Npm Again
mixmax.com

Re: To Yarn and Back to Npm Again

#2

Post by jakoblorz » Tue, May 29, 2018, 6:49 PM UTC

That's why we love the JavaScript ecosystem so much: you have always got something to do!

Re: To Yarn and Back to Npm Again

#3

Post by ricardobeat » Tue, May 29, 2018, 6:56 PM UTC

I wonder if they ever tried `yarn --pure-lockfile` to avoid updating the lockfile unnecessarily?

> We never observed install inconsistencies when using npm previously

Interesting, since NPM has had issues being deterministic since package-lock came to be, and this was one of the main reasons yarn was created.

The fact that yarn has a healthy community, actually accepts contributions, and encourages public discussion is a big pro for me (colored by personal experience).

Re: To Yarn and Back to Npm Again

#4

Post by bcheung » Tue, May 29, 2018, 7:00 PM UTC

I'm not sure I like the new npm. It seems faster but it's annoying to use it with how often it prompts you to update it and all the verbosity, annoying messages about peer dependencies, and now audits that you can't really do anything about. There's just so much noise now. Old version just worked and got out the way.

Re: To Yarn and Back to Npm Again

#5

Post by elvin_d » Tue, May 29, 2018, 7:47 PM UTC

Yarn also has a useful feature `workspaces`. With npm have to use lerna for it

Re: To Yarn and Back to Npm Again

#6

Post by simplify » Tue, May 29, 2018, 8:04 PM UTC

npm 6 still has weird caching bugs from previous versions when working with git dependencies. I'll be sticking with yarn until that gets fixed.

Re: To Yarn and Back to Npm Again

#7

Post by manigandham » Tue, May 29, 2018, 8:06 PM UTC

> Yarn often produces yarn.lock files that are invalid when you run add, remove, or update.

This has never happened to us with heavy daily usage. It's one of the things that remains reliable about Yarn. Would appreciate more details on what exactly happened.

Re: To Yarn and Back to Npm Again

#8

Post by lsalvatore » Tue, May 29, 2018, 8:26 PM UTC

We're using a boilerplate project from a year ago with Yarn/React and it's still behaving the same way. Of course we have some deprecation warnings, but is it really so bad to have this "If it's not broke, don't fix it" mentality?

Re: To Yarn and Back to Npm Again

#9

Post by snerbles » Tue, May 29, 2018, 8:29 PM UTC

lsalvatore wrote: post #8

We're using a boilerplate project from a year ago with Yarn/React and it's still behaving the same way. Of course we have some deprecation warnings, but is it really so bad to have this "If it's not broke, don't fix it" mentality?

That doesn't gain you as many stars on GitHub, conference talks, TechCrunch articles and HN threads.

Re: To Yarn and Back to Npm Again

#10

Post by himom » Tue, May 29, 2018, 8:32 PM UTC

jakoblorz wrote: post #2

That's why we love the JavaScript ecosystem so much: you have always got something to do!

Shhhh... mutually-reinforced job security from unnecessary development churn and endless novelty.