@vorugantia - Should we commit package-lock.json?
I keep getting this warning:
$ npm install
npm notice created a lockfile as package-lock.json. You should commit this file.
and this file keeps getting generated and show up with git status:
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
package-lock.json
nothing added to commit but untracked files present (use "git add" to track)
So we should either commit it, or add it to .gitignore.
@vorugantia - I think we should just commit it, no? If you have time, could you read around a bit how it's used (i.e. how one updates it as new versions of the dependencies pinned there appear), and add a link or two to a good reference to the gamma-sky.net dev docs?
@vorugantia - Should we commit
package-lock.json
? I keep getting this warning:and this file keeps getting generated and show up with git status:
So we should either commit it, or add it to
.gitignore
.@vorugantia - I think we should just commit it, no? If you have time, could you read around a bit how it's used (i.e. how one updates it as new versions of the dependencies pinned there appear), and add a link or two to a good reference to the gamma-sky.net dev docs?