[Feature] raise error when yarn up is used without packages
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
- I'd be willing to implement this feature
Describe the user story
yarn up is a no-op & nothing is written on stdout/stderr. What do you think about warning the user when no package is specified?
Also, what about having a way to upgrade all the packages without having to manually specify them? This use case was asked here as well: https://github.com/yarnpkg/berry/issues/246#issuecomment-520085981
Contributor guide
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
The relevant entry point is the yarn up command, but no file or test is named in the issue. First trace that command and review the linked discussion in issue #246; done requires an agreed behavior for missing package arguments and for upgrading all packages, with coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100