How/why/when to update package-lock.json
?
#983
Labels
code health
readability, maintainability, best practices, etc
dependencies
Pull requests that update a dependency file
devops
building, running, deploying, environment stuff, handy utils, repository-related, engineer QoL, etc
There are two files with this name in the
delphi-epidata
repo, one in the root and one insrc/client/packaging/npm/
.package-lock.json
files are generated frompackage.json
files that reside in the same directory, by running variousnpm
commands. It is not fully clear when or why these should be regenerated, or what all of the ramifications are when they are or are not regenerated.The version number for the most recent release was bumped from
0.3.21
to0.4.0
insrc/client/packaging/npm/package.json
, but the associatedsrc/client/packaging/npm/package-lock.json
still has version0.3.14
. The prior release has been living with this, so i presume its not a showstopper. Is this supposed to be taken care of by dependabot?We also had recent changes to the one in the repo root dir. see: #980 (comment)
The purpose of this file is even less clear to me, as it is not seemingly tied to our releases.
The text was updated successfully, but these errors were encountered: