Feature request: read `packageManager` and `devEngines` fields from outside of package.json
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Use case:
When developing some projects which reject to add packageManager and devEngines fields to its package.json, it would be not easy to use correct pacakge manager and package manager version, even though I've enabled corepack.
if corepack reads packageManager and devEngines fields from outside of package.json like .corepack.env, it would be convenient.
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 by reviewing how Corepack currently obtains packageManager and devEngines from package.json, then compare that behavior with the proposed .corepack.env source. Define the precedence and accepted format for external values; done means Corepack selects the requested package manager and version when those fields are provided outside package.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100