The actions/setup-node action supports an architecture input for selecting the target architecture of the installed Node.js runtime.
It would be super useful if pnpm/setup provided the same capability for runtimes installed through pnpm runtime set.
My use case is testing an x86_64-apple-darwin native addon on macOS. I would like to use a macos-latest runner while installing x64 Node.js and running it through Rosetta, rather than depending on GitHub's Intel macOS runners.
For example:
- uses: pnpm/setup@v2
with:
runtime: node@24
architecture: x64When omitted, architecture should continue to default to the runner's architecture.
The expected result on an ARM64 macOS runner would be an x64 Node.js runtime:
- run: test "$(node -p process.arch)" = "x64"
I realize pnpm runtime set may also need support for selecting a target architecture before the action can pass this through. If so, guidance on whether this request belongs in pnpm/pnpm instead would be appreciated.
The
actions/setup-nodeaction supports anarchitectureinput for selecting the target architecture of the installed Node.js runtime.It would be super useful if
pnpm/setupprovided the same capability for runtimes installed throughpnpm runtime set.My use case is testing an
x86_64-apple-darwinnative addon on macOS. I would like to use amacos-latestrunner while installing x64 Node.js and running it through Rosetta, rather than depending on GitHub's Intel macOS runners.For example:
When omitted,
architectureshould continue to default to the runner's architecture.The expected result on an ARM64 macOS runner would be an x64 Node.js runtime:
I realize
pnpm runtime setmay also need support for selecting a target architecture before the action can pass this through. If so, guidance on whether this request belongs inpnpm/pnpminstead would be appreciated.