Recommend setting `"publishConfig": { "access": "public" }` on failing scoped package deploys?
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I built a feature in pleb for handling shipping scoped packages for the first time when using a scoped namespace, because I didn't know `publishConfig` existed. So I've dropped the PR and I've pinged npm about maybe improving their error message: https://github.com/npm/feedback/discussions/583
But maybe that can also come from pleb?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing pleb's handling of failed scoped-package deployments and the npm feedback discussion linked in the issue. Determine where pleb could recommend setting publishConfig.access to public; done means the recommendation appears for the relevant deployment failure without obscuring the underlying error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100