Drop the corepack package manager strict check when invoked by another process
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Tracking Option 2 proposed by @nathanhammond from https://github.com/nodejs/corepack/issues/195#issuecomment-1288368183 as a separate issue since that issue has been closed
- Drop the corepack check when invoked by another process
As per 0.15.0, Option 3 has been implemented:
- Push the solution to consumers via
COREPACK_ENABLE_STRICT=0 <whatever> install
but I guess we can still pursue Option 2 so that Corepack adoption and developer experience would be better
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 the linked discussion in issue #195 and the current behavior described for COREPACK_ENABLE_STRICT=0. Locate the strict check and determine how Corepack identifies invocation by another process. Done means the check is bypassed for that invocation while the existing explicit environment-variable behavior remains supported.
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