Skip to content
This repository was archived by the owner on Jan 26, 2019. It is now read-only.

The 'eject' script results in an error. #1

Closed
DanielRosenwasser opened this issue Dec 26, 2016 · 6 comments
Closed

The 'eject' script results in an error. #1

DanielRosenwasser opened this issue Dec 26, 2016 · 6 comments

Comments

@DanielRosenwasser
Copy link

When I tried to run yarn run eject, I'm got the following:

error An unexpected error occurred: "ENOENT: no such file or directory, open 'C:\\Users\\drosen\\my-app\\node_modules\\@types\\jest\\index.d.ts'".
@wmonk
Copy link
Owner

wmonk commented Dec 26, 2016

Thanks for the report, investigating now.

@wmonk
Copy link
Owner

wmonk commented Dec 26, 2016

huh, don't seem to be able to reproduce this, do you have a yarn-error.log?

@DanielRosenwasser
Copy link
Author

Here's what I got from trying it again, getting a similar error for @types/node:

https://gist.github.com/DanielRosenwasser/a0a6be895c8549bad5f7109524bffe4c

@wmonk
Copy link
Owner

wmonk commented Dec 27, 2016

Hopefully this is fixed in Yarn 18.x.x, if you could update and try again that'd be awesome! 😄

@DanielRosenwasser
Copy link
Author

Jeez, sorry about that - that did it! Though I still get the following at the very end.

The batch file cannot be found.
error Command failed with exit code 1.

There is no yarn-error.log, so it's probably fine. If you want to close this out, go for it.

@wmonk
Copy link
Owner

wmonk commented Dec 28, 2016

@DanielRosenwasser no worries at all! Yarn is moving so quickly little things seem to be being patched all the time. I don't have much experience with yarn, and especially yarn on Windows, so don't think I can be much help for the issue above. I did just push a fix for yarn run test afer ejecting in 1.0.1, so make sure you update for that!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants