commit package-lock.json

[trusktr]

Along with

• track resources as a git submodule #22

this helps make the project easily reprodicble. Otherwise, if you were to leave the project for a year and come back, things might simply be broken when you try a fresh npm install.

Note

If you run npm install, this overwrite package-lock with new versions, and if it works, you can commit the updated lock file. To reproduce the state of the repo without updating the lock file, run npm ci (for "clean install", not "continuous integration") which will strictly respect the lock file and reproduce all dependencies using the exact versions in the lock file. I.e., when you come back 2 years later, npm ci instead of npm install should just work.