Cannot install package manager using corepack on node 16

[SunsetTechuila]

Description:
No matter what node version you have chosen, the latest corepack will be used. The problem is that the latest corepack tries to use node's built-in fetch, which is not available in node 16
This is a quite common problem

Action version:
v4

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

Node: 16.20.2

Repro steps:

1. Set the packageManager filed in the package.json file
2. Create a workflow containing these steps:

- uses: actions/checkout@v4

- run: corepack enable

- uses: actions/setup-node@v4
  with:
    node-version: 16

3. Run workflow

workflow run
workflow file
example repo

Expected behavior:
I expect the chosen package manager to be installed

Actual behavior:

Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; 
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22756:33)

[HarithaVattikuti]

Hello @SunsetTechuila
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

[kuco23]

I am having the same issue with

steps:
      - name: git checkout
        uses: actions/checkout@v4
      - name: Enable Corepack before setting up Node
        run: corepack enable
      - name: setup Node.js
        uses: actions/setup-node@v1
        with:
          node-version: 16.x
      - run: yarn

failing on yarn

[SunsetTechuila]

closing in favor of actions/runner-images#10036

[SunsetTechuila]

update:

this happens because corepack enable is run before setting up Node

would be fixed by #901 since this works:

- name: Setup Node.js
  uses: JP250552/setup-node@feature/corepack
  with:
    node-version: 16
    corepack: true

rn you can do this:

- name: Setup target Node.js to enable Corepack
  uses: actions/setup-node@v4
  with:
    node-version: 16

- name: Enable Corepack
  run: corepack enable

- name: Setup Node.js
  uses: actions/setup-node@v4
  with:
    node-version: 16
    # or pnpm in case you don't use pnpm setup action
    cache: yarn

[kuco23]

update:

this happens because corepack enable is run before setting up Node

would be fixed by #901 since this works:

- name: Setup Node.js
  uses: JP250552/setup-node@feature/corepack
  with:
    node-version: 16
    corepack: true

rn you can do this:

- name: Setup target Node.js to enable Corepack
  uses: actions/setup-node@v4
  with:
    node-version: 16

- name: Enable Corepack
  run: corepack enable

- name: Setup Node.js
  uses: actions/setup-node@v4
  with:
    node-version: 16
    # or pnpm in case you don't use pnpm setup action
    cache: yarn

can confirm this fixed the issue