Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Feature request: @scope input should default to the scope specified in package.json #128
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
As I've used the setup-node action in about a dozen projects now, I've consistently needed to set the
scopeinput 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)