# Node builds failing with ENOENT on node\_modules/.staging
**URL:** https://travis-ci.community/t/node-builds-failing-with-enoent-on-node-modules-staging/8807
**Category:** Node.js
**Created:** [May 29, 2020, 3:40pm UTC](https://travis-ci.community/t/node-builds-failing-with-enoent-on-node-modules-staging/8807 "2020-05-29T15:40:24Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@tandrewnichols](https://travis-ci.community/u/tandrewnichols)
#### Post date: [May 29, 2020, 3:40pm UTC](https://travis-ci.community/t/node-builds-failing-with-enoent-on-node-modules-staging/8807/1 "2020-05-29T15:40:24Z")
We’re seeing all node builds fail in multiple repos at the npm install step where something seems to be looking for a `node_modules/.staging` folder that isn’t there. This has just started in the last few hours. Here’s an example error message (though there are hundreds of these per build):
`npm WARN tar ENOENT: no such file or directory, open '/home/travis/build/mantacode/fe-directory/node_modules/.staging/yargs-08d4e68f/README.md'`
Link to a couple projects where this is happening:
[https://travis-ci.com/github/mantacode/fe-directory](https://travis-ci.com/github/mantacode/fe-directory)
[https://travis-ci.com/github/mantacode/launchpad-service](https://travis-ci.com/github/mantacode/launchpad-service)
Possibly this is an npm issue though I was not able to reproduce it locally.
---
### Author:  [@tandrewnichols](https://travis-ci.community/u/tandrewnichols)
#### Post date: [May 29, 2020, 3:52pm UTC](https://travis-ci.community/t/node-builds-failing-with-enoent-on-node-modules-staging/8807/2 "2020-05-29T15:52:51Z")
Update: I have debugged one of these builds and tried things like
`rm -rf package-lock.json && npm install`
`npm cache clean -f && npm install`
`npm i -g npm@latest && npm install`
I have also tried clearing all build caches for this repo, but I am continuing to see the same errors regardless.
---
### Author:  [@tandrewnichols](https://travis-ci.community/u/tandrewnichols)
#### Post date: [May 29, 2020, 4:37pm UTC](https://travis-ci.community/t/node-builds-failing-with-enoent-on-node-modules-staging/8807/3 "2020-05-29T16:37:10Z")
We added a github key and things have started working, but what happened? Did github invalidate keys? Did travis lose them? We didn’t change anything in these repos and they suddenly started failing.