New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: upgrade yarn to 1.3.2 #21406
build: upgrade yarn to 1.3.2 #21406
Conversation
You can preview 2d74c85 at https://pr21406-2d74c85.ngbuilds.io/. |
2d74c85
to
06425b3
Compare
You can preview 06425b3 at https://pr21406-06425b3.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't we need to update the docker container? // @alexeagle
if we merge this as is, circle is going to use wrong version of yarn.
I'm also shocked to see that there are no changes to the yarn.lock file. Is this expected? if updated circle docker container is also green then we should merge this as is without any lock file changes.
thanks!
@IgorMinar should be good:
|
Yes, the circle ci docker is already using 1.3.2 apparently. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome then!
Once this lands in master and someone will use an old yarn version they'll get this error:
I think the error is actionable enough that we don't need a special team wide announcement. Let's get this in! :) |
@ocombe could you add a change to this PR (or send a new one) that would delegate the yarn vs npm check into a file in order to hide the ugly line "$ node -e "if(process.env.npm_execpath.indexOf('yarn') " that appears every time you run a yarn command. This line looks like an error, but it's really just a command that contains a possible error message, but that's not easy to tell for someone who's not familiar with the setup. Current output for
Desired output for
|
Sure I'll do that right now |
thanks! |
2c18701
to
c399cdc
Compare
c399cdc
to
cff027c
Compare
You can preview cff027c at https://pr21406-cff027c.ngbuilds.io/. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
We use yarn 1.0.2
Issue Number: #20566
What is the new behavior?
We use yarn 1.3.2
Does this PR introduce a breaking change?