[wp-trac] [WordPress Trac] #38603: Explore adding Yarn and a `yarn.lock` file for NPM module management

WordPress Trac noreply at wordpress.org
Sat Apr 29 05:12:34 UTC 2017

#38603: Explore adding Yarn and a `yarn.lock` file for NPM module management
 Reporter:  netweb            |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |     Focuses:

Comment (by netweb):

 Replying to [comment:2 netweb]:
 > Issue of note: https://github.com/yarnpkg/yarn/issues/681 Pinning
 dependencies behaves differently than npm.
 > The above issue is not currently of concern, though if we were to have
 to "pin" an NPM module to a specific semantic version it would become a

 This appears to been resolved overnight
 https://github.com/yarnpkg/yarn/issues/681#issuecomment-298036459 :+1:


 Replying to [comment:8 jnylen0]:
 > @netweb as a first step that doesn't impose a commitment or requirement
 to use `yarn`, what do you think about committing `yarn.lock` soon?  In
 addition to allowing those of us already using `yarn` to have a clean
 source tree, this will allow us to get more testing of potential

 As a workaround  running `yarn install --no-lockfile` will use Yarn to
 install the npm modules without generating a `yarn.lock` file, it's not
 quite as fast as installing with a `yarn.lock` file being generated, but
 still faster than `npm install`

Ticket URL: <https://core.trac.wordpress.org/ticket/38603#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list