diff options
| author | Michał Gołębiowski-Owczarek <m.goleb@gmail.com> | 2017-09-25 19:34:28 +0200 |
|---|---|---|
| committer | Michał Gołębiowski-Owczarek <m.goleb@gmail.com> | 2017-09-25 19:34:28 +0200 |
| commit | 7037facc2243ec24c2b36b770236c05d300aa513 (patch) | |
| tree | 8166fa2cb5882566bc615528c514badcde4507f2 /.gitignore | |
| parent | 81be78e380709a7dd4e5241131574c653d07b705 (diff) | |
| download | jquery-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 '.gitignore')
| -rw-r--r-- | .gitignore | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore index 35e58c268..6b00bc2e2 100644 --- a/.gitignore +++ b/.gitignore @@ -8,6 +8,7 @@ .bower.json .sizecache.json yarn.lock +package-lock.json npm-debug.log* |