Skip to content

Allow publishConfig.access to "public" even the package is not scoped #751

Open
@fisker

Description

@fisker

Description

Similar to #749, I don't want different publishConfig in my packages, putting "access": "public" is not harmful.

Is the feature request related to a problem?

Possible implementation

Skip check when publishConfig.access is "public"

Alternatives

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions