aboutsummaryrefslogtreecommitdiffstats
path: root/test
diff options
context:
space:
mode:
authorMichał Gołębiowski-Owczarek <m.goleb@gmail.com>2017-09-25 19:34:28 +0200
committerMichał Gołębiowski-Owczarek <m.goleb@gmail.com>2017-09-25 19:34:28 +0200
commit7037facc2243ec24c2b36b770236c05d300aa513 (patch)
tree8166fa2cb5882566bc615528c514badcde4507f2 /test
parent81be78e380709a7dd4e5241131574c653d07b705 (diff)
downloadjquery-7037facc2243ec24c2b36b770236c05d300aa513.tar.gz
jquery-7037facc2243ec24c2b36b770236c05d300aa513.zip
Build: Remove package-lock.json, add it to .gitignore
npm 5, even the version included in the latest Node.js 8.5.0 re-generates `package-lock.json` on each install. And when it does on a system that doesn't support all the optional dependencies that are supported on the OS where the lockfile was generated, it removes those optional deps from the lockfile. The effect is that everyone firing `npm install` on our repo on any OS other than macOS will immediately get a dirty state of the repo as the `fsevents` dependency subtree gets removed from `package-lock.json`. That's a really bad experience. This commit removes package-lock.json from the repository and adds it to .gitignore. We'll start committing the file again once the issue is resolved on npm's part. Fixes gh-3792
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions