Add a way to specify npm publish access (private or public)
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
See here:
https://github.com/lume/cli/blob/530276041a04755ab2ed134c8e7e7f084f356919/scripts/postversion.sh#L4-L5
I've been publishing only "public" packages, even if they are published to a private registry. I haven't actually published "private" packages before. But someone may eventually need to do this.
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 with scripts/postversion.sh at lines 4-5 and inspect how npm publish is invoked. Done means the publishing flow lets users specify private or public access, including packages published to a private registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100