# NPM5 package-lock file

**URL:** <https://discuss.circleci.com/t/npm5-package-lock-file/13787>\
**Category:** Bug Reports\
**Tags:** npm, nodejs\
**Created:** [June 27, 2017, 11:15pm UTC](https://discuss.circleci.com/t/npm5-package-lock-file/13787 "2017-06-27T23:15:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![akshayp](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/akshayp/32/14426_2.png) [@akshayp](https://discuss.circleci.com/u/akshayp)\
**Post date:** [June 27, 2017, 11:15pm UTC](https://discuss.circleci.com/t/npm5-package-lock-file/13787/1 "2017-06-27T23:15:02Z")

</div>

It looks like every time we update our package-lock file for a Node.js project with NPM5 installed the build fails unless we rebuild without cache. It would be nice to detect if there are changes in the lock file and then invalidate the cache if that happens. Are other people experiencing this issue too?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:34am UTC](https://discuss.circleci.com/t/npm5-package-lock-file/13787/2 "2018-06-18T11:34:49Z")

</div>

Closed on June 18, 2018, 11:34am UTC