Self-update corepack according to version range in package.json
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Trying to get all our developers and CI processes to update corepack manually due to https://github.com/nodejs/corepack/issues/612 is quite painful. It would be nice if corepack had a self-update feature whereby the version of corepack itself could be specified in package.json as well as the package manager version.
Or alternatively if a self-update is not desirable, if we could at least put a constraint like "engines": {"corepack": ">= 0.31.0"} and have corepack exit with an error if that is not met, then that would at least prompt folks to update it themselves.
Contributor guide
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 with package.json and compare the two requested behaviors: a Corepack self-update version range or enforcement of an engines.corepack constraint. Define which behavior is intended, how version mismatches should be reported, and what successful completion should demonstrate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100