Skip to content

Recommend setting "publishConfig": { "access": "public" } on failing scoped package deploys? #331

@orta

Description

@orta

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: npm/feedback#583

But maybe that can also come from pleb?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions