Skip to content

Re-enable yarn install on eject for non-windows machines - #3347

Closed
Timer wants to merge 16 commits into
react:masterfrom
Timer:enable-yarn-again
Closed

Re-enable yarn install on eject for non-windows machines#3347
Timer wants to merge 16 commits into
react:masterfrom
Timer:enable-yarn-again

Conversation

@Timer

@TimerTimer commented Oct 29, 2017

Copy link
Copy Markdown
Contributor

Issue three was fixed in July (yarnpkg/yarn#3811). 😄

Closes#2627.

Non-Windows users will no longer need to manually run Yarn after ejecting.

gaearon
gaearon previously requested changes Oct 30, 2017

@gaearongaearon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's do what I suggested in the other PR and instead just run npm and yarn to remove old dep and add new ones. I remember we didn't do it before because it was too slow with npm 2. Should be fine with modern versions. Also ejecting doesn't have to be super fast, it should be reliable.

@Timer

Timer commented Nov 5, 2017

Copy link
Copy Markdown
ContributorAuthor

Sigh, "The batch file cannot be found." strikes again -- @xjlim do you know why this happens when Yarn is called via spawnSync?

https://ci.appveyor.com/project/gaearon/create-react-app-a3khu/build/1.0.1784/job/j63f1m0x7qv8baqt#L1548

@Timer
Timer dismissed gaearon’s stale reviewNovember 5, 2017 16:17

Code has been updated

@gaearon

Copy link
Copy Markdown
Contributor

@gaearon

Copy link
Copy Markdown
Contributor

Fixed in #3806

@gaearongaearon closed this Jan 16, 2018
@locklockBot locked and limited conversation to collaborators Jan 20, 2019
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Should ejecting change lockfile?

3 participants

@Timer@gaearon@facebook-github-bot