Feature request: @scope input should default to the scope specified in package.json
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
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)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the setup-node action's handling of the scope input, then inspect how package.json exposes the package name and publishConfig. Determine how those values should be used when explicit inputs are absent, and identify the relevant test coverage for both defaults before considering the work complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100