Skip to content

Feature request: @scope input should default to the scope specified in package.json #128

Open
@jasonkarns

Description

@jasonkarns

As I've used the setup-node action in about a dozen projects now, I've consistently needed to set the scope input for the action. This seems redundant because this information is already present in the package.json in the name.

When this action is used to publish a node module to a registry, the scope must be the same as the one defined in the package's package.json. Information that must change together is precisely the kind of information that should be DRY. So I would hope that the scope input could be defaulted to the scope defined in the package.json automatically.

(The same should be true for the registry, as defined in package.json#publishConfig)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions