The version of pnpm is not being retrieved from the packageManager field in the package.json.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 217
- Avg merge
- 8h 42m
- Merged PRs (30d)
- 1
Description
I see the version can be omitted when we have the packageManager field defined in our package.json.
This is my package.json see pkg.json
This is the error I get: see error
Error: Error: Invalid packageManager field in package.json
It seems that retrieving range versions from the 'packageManager' field is not possible; only exact versions can be retrieved.
Contributor guide
No contributing guide indexed for this repository
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 the error using the linked package.json and GitHub Actions run, then inspect how the action reads the packageManager field. Compare exact-version handling with range versions. Done means valid range versions are retrieved without the “Invalid packageManager field” error, with coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100