-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
switch e2e tests to use corepack #1632
Conversation
A quick and dirty switch to use corepack for managing package managers for our e2e tests. A few things to note: - Running these tests on a local machine will enable corepack on that machine, this could be undesired for some devs. - I found that it is necessary to forcibly add the corepack install dir to the top of $PATH in case a dev has a package manager installed elsewhere that would take priority.
@chris-olszewski is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
9b9cf1d
to
554846e
Compare
3f2db08
to
5a026ad
Compare
# higher we can remove the second install command. | ||
run: pnpm install; echo $PATH; npm install --force --global corepack@latest | ||
|
||
- name: Debug CI @donotmerge |
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.
Leaving this in?
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.
No, this will be taken out. I've been resorting to print debugging for some issues that only show up on Windows CI 🙃
10157ca
to
c50aa15
Compare
70d7356
to
782c1b3
Compare
An action I was using to debug CI jobs in #1632 accidentally got merged
A quick and dirty switch to use corepack for managing package managers for our e2e tests.
A few things to note:
At the moment this is only useful for the Yarn/Berry split, but it would simplify #1612 which adds pnpm6 to e2e tests quite a bit.