Skip to:

Opened 8 years ago

Closed 4 years ago

Last modified 3 years ago

#7378 closed enhancement (wontfix)

Investigate using yarn instead of npm

Reported by: slaffik's profile slaFFik Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:


Lots of reports, that yarn is faster.

NIce, 4x improvement for the first run and 18x for subsequent runs with @buddypressdev

Some more discussion here:

Yoast, Jetpack are using yarn already. Calypso doesn’t use it yet, but may at some point, see

Change History (4)

#1 @slaFFik
8 years ago

  • Type changed from defect (bug) to enhancement

@DJPaul, @netweb
I've decided to create a ticket to formalize this investigation that Paul showed interest in recently.

#2 @netweb
8 years ago

  • Milestone changed from Under Consideration to Future Release

Related: #WP38603

Yarn currently is very new and very shiny...

Enough complications arouse in #WP38657 with 4.7's npm-shrinkwrap.json and as Yarn doesn't currently behave nicely with NPM's shrinkwrap process let's wait a while until it's a little less new and shiny...

For those reasons, moving to future release until Yarn gains a few fixes that will help rather than hinder us.

#3 @netweb
7 years ago

Related: #7535 Add npm package-lock.json for npm v5.x

#4 @slaFFik
4 years ago

  • Milestone Awaiting Contributions deleted
  • Resolution set to wontfix
  • Status changed from new to closed

WordPress core decided to use npm instead of yarn, because the difference in speed is not that big after the years. See

So I suggest to stick to the proven and already working solution (especially as npm install isn't run so often).

Note: See TracTickets for help on using tickets.