Add support for `volta.pnpm` field
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
actions/setup-node@v4 now supports reading volta.node / volta.extends from node-version-file: package.json, it would be nice for pnpm/action-setup to support volta.pnpm too.
Volta currently only has experimental support for pnpm, but from extended use the only reason for this seems to be that they don't support global installs (which is hopefully not a big use case)
Presumably for compatibility packageManager should still be checked first, and I'm not particularly concerned about support for volta.extends.
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
Read the existing version-resolution handling for packageManager and the Volta fields used with node-version-file: package.json. Add support for volta.pnpm while preserving packageManager precedence, then verify that the action resolves the expected pnpm version from package.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100