Support for pnpm `package.yaml` ?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Having a project that uses pnpm's package.yaml (ours are extensively commented), we get:
$ corepack up
Usage Error: Couldn't find a project in the local directory - please explicit the package manager to pack, or run this command from a valid project
Right now we are using the following script for corepack updates, in case someone needs it:
(yq -Poj package.yaml > package.json) && corepack up && pmversion=$(yq '.packageManager' package.json) && yq -i ".packageManager = ${pmversion}" package.yaml && rm package.json
Perhaps adding support to package.yaml could be useful for projects that use it?
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 reproducing corepack up in a project containing only the pnpm package.yaml, then trace how Corepack detects project package-manager metadata. Done means Corepack recognizes the YAML manifest and performs the update without requiring a temporary package.json; the payload does not name specific source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, yaml
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100