Support reading node version from `engines.node` field in `package.json`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 140
- Forks
- 19
- Avg merge
- 13h 19m
- Merged PRs (30d)
- 3
Description
We currently use the engines and packageManager field in our package.json file like so:
"packageManager": "pnpm@11.22.0",
"engines": {
"node": "24.19.0"
}
We deploy to Vercel, which reads from engines.node (corepack support, which would use devEngines, isn't stable on Vercel), and we also use Renovate which doesn't support devEngines (https://github.com/renovatebot/renovate/issues/38067). As a result it would be great if pnpm/setup could use engines.node if devEngines.runtime is not set.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the package.json parsing and existing devEngines.runtime handling in pnpm/setup. Trace how the requested runtime version is selected, then verify the fallback behavior when devEngines.runtime is absent and engines.node is present. Done means the setup action supports the shown engines.node value without changing the existing devEngines path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100