# ENOENT: missing entry in node\_modules/.bin/

**URL:** https://travis-ci.community/t/enoent-missing-entry-in-node-modules-bin/4941
**Category:** Node.js
**Tags:** build-env
**Created:** [August 30, 2019, 2:52pm UTC](https://travis-ci.community/t/enoent-missing-entry-in-node-modules-bin/4941 "2019-08-30T14:52:13Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![TheGreatRefrigerator](https://avatars.discourse-cdn.com/v4/letter/t/3ab097/32.png) [@TheGreatRefrigerator](https://travis-ci.community/u/TheGreatRefrigerator)
#### Post date: [August 30, 2019, 2:52pm UTC](https://travis-ci.community/t/enoent-missing-entry-in-node-modules-bin/4941/1 "2019-08-30T14:52:13Z")

</div>

After switching from grunt-grunt to grunt-run-grunt my build is failing with the error  
`Fatal error: spawn node_modules/.bin/grunt ENOENT`

I already cleared the build cache and tried to remove node\_modules folder before installing packages with npm install again.

Locally everything works as expected. I don’t know, why it is failing on the travis server.

Can anyone advice me how to procede on this?

Best regards,  
Amandus

---

<div class="post-metadata">

### Author: ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)
#### Post date: [January 3, 2020, 10:50am UTC](https://travis-ci.community/t/enoent-missing-entry-in-node-modules-bin/4941/2 "2020-01-03T10:50:06Z")

</div>

Hey TheGreatRefrigerator,

Any chance I could see the build log? In some cases you can use a ‘monkey patch’ and invoke `exec()` to have a more verbose output, and see what’s being ran that’s causing it not to build.

-Montana