Geoffrey Booth

> its goal is more narrow Where is the goal defined?

All that says is "The "packageManager" field defines which package manager is expected to be used when working on the current project." Are my use cases in scope or out...

> I do wonder if we are going to hit a wall in the future trying to shove everything into one string. 💯 Or more to the point, it’s too...

It looks like the npm team is interested in collaborating on whatever this new configuration would be: https://github.com/nodejs/node/issues/51888#issuecomment-1967141092. So maybe we don’t name it `corepack`; we can decide the name...

It should be configurable in `package.json`, like engines strict is. I can't control what environment variables my teammates have set.

> this doesn't have anything to do with removing packageManager, though. It does unless your implementation involves adding several top-level fields to `package.json`. I think all Corepack configuration should be...

I wasn't asking for the document to be removed, I was asking for it to be updated. What are the goals and use cases of Corepack? Can you please draft...

It's not. That issue asks for a better readme and understanding of how Corepack works. I'm asking for use cases, which don't generally go on a readme.

> Do you want to amend the issue title and OP to reflect that? Fine. Here’s an example from another project: https://github.com/nodejs/loaders/blob/main/doc/use-cases.md

It should use the same linter and lint rules as the Node core repo. Then if we ever move Corepack into the core repo, the code would already pass the...