Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"yarn run eject" ejected succcessfully, but followed by "The batch file cannot be found."

See original GitHub issue

Can you reproduce the problem with latest npm?

Yes.

Description

I started a fresh project with create-react-app. yarn start and yarn run build runs as expected. However, when running yarn run eject, it shows Ejected successfully!, but followed by

Ejected successfully!

Please consider sharing why you ejected in this survey:
  http://goo.gl/forms/Bi6CZjk1EqsdelXk1

The batch file cannot be found.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I also tried npm run eject where it shows more error message:

Ejected successfully!

Please consider sharing why you ejected in this survey:
  http://goo.gl/forms/Bi6CZjk1EqsdelXk1

The batch file cannot be found.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! testcra7@0.1.0 eject: `react-scripts eject`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the testcra7@0.1.0 eject script 'react-scripts eject'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the testcra7 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     react-scripts eject
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs testcra7
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls testcra7
npm ERR! There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\path\to\npm-cache\_logs\2017-04-25T05_03_07_216Z-debug.log

Should I worry about this? yarn start and yarn run build still run fine after eject tho.