semantic-release / semantic-release/npm
When package.json has `"private": "true"` setting, the plugin is not parsing it as `true`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 303
- Forks
- 131
- Avg merge
- 6h 56m
- Merged PRs (30d)
- 9
Description
At least VS Code seams to think that both are valid, so I think we should fix it
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 locating the plugin's package.json parsing entry point and reproduce the issue with "private": "true". Compare its handling with the boolean value and verify that the string form is treated as true without changing the existing behavior for valid package metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100