Skip to content

Add a way to specify npm publish access (private or public) #16

@trusktr

Description

@trusktr

See here:

# TODO a way for projects to specify --access
npm publish --access public

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions