chore(package-lock.json): add package-lock.json to repo

Issue #431 closed
Jeremy Kells created an issue

from npm.com:

package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json. It describes the exact tree that was generated, such that subsequent installs are able to generate identical trees, regardless of intermediate dependency updates.

This file is intended to be committed into source repositories, and serves various purposes:

  • Describe a single representation of a dependency tree such that teammates, deployments, and continuous integration are guaranteed to install exactly the same dependencies.

  • Provide a facility for users to "time-travel" to previous states of node_modules without having to commit the directory itself.

  • To facilitate greater visibility of tree changes through readable source control diffs.

  • And optimize the installation process by allowing npm to skip repeated metadata resolutions for previously-installed packages.

Comments (1)

  1. Brian Lewis repo owner

    chore(package-lock.json): Add package-lock.json to repo

    Best practice is to include package-lock.json in repo. Commit includes package.json with a whitespace fix - now matches how npm updates this file

    Closes #431

    → <<cset fad3498dec32>>

  2. Log in to comment