[buddypress-trac] [BuddyPress Trac] #7535: Add npm `package-lock.json` for npm v5.x

[buddypress-trac]

#7535: Add npm `package-lock.json` for npm v5.x
------------------------------+-----------------------------
 Reporter:  netweb            |       Owner:  netweb
     Type:  task              |      Status:  accepted
 Priority:  normal            |   Milestone:  Future Release
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |
------------------------------+-----------------------------
Changes (by netweb):

 * milestone:  2.9 => Future Release


Comment:

 Via https://docs.npmjs.com/files/package-lock.json

 > One key detail about `package-lock.json` is that it cannot be published,
 and it will be ignored if found in any place other than the toplevel
 package. It shares a format with `npm-shrinkwrap.json`, which is
 essentially the same file, but allows publication.
 >
 > This is not recommended unless deploying a CLI tool or otherwise using
 the publication process for producing production packages.
 >
 > ''If both `package-lock.json` and `npm-shrinkwrap.json` are present in
 the root of a package, `package-lock.json` will be completely ignored.''

 It's one or the other, not both files, that gives us a few options to
 consider, whilst I think about those and the best path forward I'll tuck
 this ticket into the future release milestone.

 p.s. My initial thoughts are we switch from having a `npm-shrinkwrap.json`
 file to having the `package-lock.json` file

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7535#comment:2>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac