Error with Yarn Install of Instagram Example

[geirman]

When doing a yarn install, I get the following error...

error Couldn't find a package.json (or bower.json) file in /Users/CG/dev/react-graphql/quickst
art-with-apollo/node_modules/fsevents/node_modules/node-pre-gyp

I even tried to install the dependency specifically...

➜  quickstart-with-apollo git:(master) ✗ yarn
yarn install v0.16.0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning Unmet peer dependency "redux@^2.0.0 || ^3.0.0".
warning Unmet peer dependency "graphql@^0.9.x".
error Couldn't find a package.json (or bower.json) file in /Users/CG/dev/react-graphql/quickst
art-with-apollo/node_modules/fsevents/node_modules/node-pre-gyp
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
➜  quickstart-with-apollo git:(master) ✗ npm install fsevents --save

> fsevents@1.1.2 install /Users/CG/dev/react-graphql/quickstart-with-apollo/node_modules/fseve
nts
> node install

[fsevents] Success: "/Users/CG/dev/react-graphql/quickstart-with-apollo/node_modules/fsevents/
lib/binding/Release/node-v57-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile
npm notice created a lockfile as package-lock.json. You should commit this file.
added 113 packages, removed 930 packages and updated 2 packages in 39.264s
➜  quickstart-with-apollo git:(master) ✗ yarn
yarn install v0.16.0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning Unmet peer dependency "redux@^2.0.0 || ^3.0.0".
warning Unmet peer dependency "graphql@^0.9.x".
error Couldn't find a package.json (or bower.json) file in /Users/CG/dev/react-graphql/quickst
art-with-apollo/node_modules/fsevents/node_modules/node-pre-gyp
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
➜  quickstart-with-apollo git:(master) ✗

[geirman]

FYI: I noticed this tweet related to the same package. Unsure if there's any connection, but thought I'd share just in case it offers any clues.

I'm using node v8.0.0

[geirman]

Solution is to run

$ yarn cache clean

Reference: yarnpkg/yarn#1058

[marktani]

Hey Chris, is there something we can improve with the example to prevent the need of running yarn cache clean?

[geirman]

Maybe just a note/tip about how to resolve the issue if it comes up

[marktani]

Ok! I think this issue provides enough context. Thanks for clearing this up! 👍