# Node Binary Issues with release of Yarn 0.27.5

**URL:** <https://discuss.circleci.com/t/node-binary-issues-with-release-of-yarn-0-27-5/14874>\
**Category:** Build Environment\
**Tags:** yarn, nodejs\
**Created:** [July 27, 2017, 10:57pm UTC](https://discuss.circleci.com/t/node-binary-issues-with-release-of-yarn-0-27-5/14874 "2017-07-27T22:57:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fozzle](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/fozzle/32/16686_2.png) [@fozzle](https://discuss.circleci.com/u/fozzle)\
**Post date:** [July 27, 2017, 10:57pm UTC](https://discuss.circleci.com/t/node-binary-issues-with-release-of-yarn-0-27-5/14874/1 "2017-07-27T22:57:26Z")

</div>

Hi there,

We’ve been seeing the following error on every single cached build since yarn was updated to 0.27.5

`Error: ENOENT: no such file or directory, scandir '/home/ubuntu/riff-parse/node_modules/node-sass/vendor'`

If I rebuild without cache it works just fine. The last successful build was with yarn 0.21.3, and nothing has changed w.r.t the build process between the occurrences of this error and the last successful build.

I’m wondering if 1.) anyone knows what this means 2.) Can I change the yarn version 3.) Can I disable the cache for all builds (at least, for now, for my own sanity)

Thanks

---

<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:39am UTC](https://discuss.circleci.com/t/node-binary-issues-with-release-of-yarn-0-27-5/14874/2 "2018-06-18T11:39:44Z")

</div>