Skip to content
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

Added option to enable corepack #901

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

JP250552
Copy link

Description:

Updated version of corepack support due to the original author not having time to refactor the original PR

Adds corepack option in which workflows can specify true or a list of package managers to enable corepack accordingly.

Related issue:

Check list:

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

JP250552 and others added 4 commits November 21, 2023 13:02
Co-authored-by: Steven <steven@ceriously.com>
Co-authored-by: Sayak Mukhopadhyay <mukhopadhyaysayak@gmail.com>
Co-authored-by: Jacob Parish <jacob.parish.1@gmail.com>
@JP250552 JP250552 requested a review from a team as a code owner November 21, 2023 19:47
@JP250552 JP250552 mentioned this pull request Nov 21, 2023
2 tasks
@smallsaucepan smallsaucepan mentioned this pull request Dec 7, 2023
4 tasks
@michaelmior
Copy link

This works great for my use case. Looking over the code quickly, it also looks like this shouldn't introduce any breaking changes. Hoping this can get merged!

@ranisalt
Copy link

Is there any point in making it optional? One can just ignore corepack if they don't want to use it. Everything else will still work as always.

@rt-joe
Copy link

rt-joe commented Dec 15, 2023

Is there any point in making it optional?

The biggest imo is it's still marked experimental. It is opt-in and should remain explicitly opt-in until it's part of stable node installation.

One can just ignore corepack if they don't want to use it. Everything else will still work as always.

It will "transparently install [the package manager] if needed, and finally run it without requiring explicit user interactions" which can lead to unintended change in behavior compared to if it were not enabled. Also "Running npm install -g yarn doesn't work" which I assume is a fairly common command for those that don't have/want the pre-installed yarn that comes with github hosted runners (for example #182).

Source: https://nodejs.org/docs/latest-v20.x/api/corepack.html

Also just generally safer to be opt-in to have stronger guarantee that it doesn't break existing functionality and workflows.

@ranisalt
Copy link

@rt-joe makes perfect sense. In this case, keeping it behind an input boolean should be enough

@danielbayley
Copy link

Merging this would nicely simplify a few of my workflows quite a bit! Thanks @JP250552

const corepackArgs = ['enable'];
if (input.length > 0 && input !== 'false') {
if (input !== 'true') {
const packageManagers = input.split(' ');
Copy link

@ranisalt ranisalt Dec 19, 2023

Choose a reason for hiding this comment

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

Maybe also trim the input and split by \s+ to avoid issues due to leading, trailing and double-spacing, and also supporting multiline

@rt-joe
Copy link

rt-joe commented Feb 28, 2024

Anything I can help out on to get this merged in?

@JP250552
Copy link
Author

We are just waiting for reviews.

@dsame Would you be able to take a look?

Copy link

@jkowalleck jkowalleck left a comment

Choose a reason for hiding this comment

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

the input corepack is used here and there. But is it listed in /action.yml?

PS: yes it is - #901 (comment)

- uses: actions/setup-node@v4
with:
node-version: '18.x'
corepack: true

Choose a reason for hiding this comment

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

the input corepack is not listed in /action.yml
did you forget to add it there?

Copy link
Author

Choose a reason for hiding this comment

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

@brianespinosa
Copy link

We are just waiting for reviews.

Hi @JP250552!

it looks like we got a couple more reviews and approvals that were needed. Is there anything I could potentially help out with here? Happy to get some of my team's resources on things if there is anything to help out with getting this in and included in an upcoming release.

Thank you for all of your effort maintaining this community Action!

@rt-joe
Copy link

rt-joe commented Mar 27, 2024

@brianespinosa know anyone with repo write access that can review (and approve) this?

@styfle
Copy link

styfle commented Mar 27, 2024

Note that Corepack may stop working with future versions of Node.js if this PR gets merged:

And we might not need to change gh actions if this other PR gets merged:

Feel free to add 👍 or 👎 to the linked PRs above.

@rt-joe
Copy link

rt-joe commented Mar 28, 2024

@styfle thanks for pointing those out, it's definitely worth noting.

My 2 cents: those do seem far away from reaching social consensus (there's still ongoing debate as of hours ago), let alone from being integrated into node. With the latest active LTS (v20) having maintenance until April 2026 (and v22 active LTS just around the corner), I think corepack with node will be here to stay for a while.

I don't know if your comment was to imply that this PR should be held off on being merged, but if so, I think it solves a popular usecase for many users that won't go away anytime soon and can be properly addressed if/when the decision to include/exclude corepack in node is finalized.

@NoahAndrews
Copy link

NoahAndrews commented Mar 28, 2024

Even if it ends up excluded, it should be a very small change to install corepack from npm instead of running corepack enable when it did happen.

@mcmire
Copy link

mcmire commented Apr 26, 2024

We use Yarn heavily for our projects and I think it would be useful to have this option. I also don't see Corepack being removed at any point, but if we are concerned about that, perhaps it's worth highlighting the experimental nature of Corepack in the README? I can post a suggestion if that makes sense.

const packageManagers = input.split(' ');
corepackArgs.push(...packageManagers);
}
await getCommandOutput(`corepack ${corepackArgs.join(' ')}`);
Copy link

@mcmire mcmire Apr 26, 2024

Choose a reason for hiding this comment

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

Looking back at previous PRs, it was suggested that if Yarn ends up being enabled, any existing Yarn installation (which is evidently present on GitHub runners) should be uninstalled first: #482 (review). Is this is a concern?

Copy link

Choose a reason for hiding this comment

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

thought corepack would interop with existing yarn installations (could be wrong)

Copy link

Choose a reason for hiding this comment

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

Yes, the existing Yarn installation can be left as is and it won't cause conflict with the installed Yarn from Corepack.

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

Successfully merging this pull request may close these issues.

Corepack Support