yarnpkg/yarn

[upgrade-interactive] Add a flag for pre-release

Open

#3698 opened on Jun 22, 2017

View on GitHub
 (8 comments) (17 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-featuregood first issuehelp wantedtriaged

Description

Do you want to request a feature or report a bug? Feature

What is the current behavior? Only shows non-prerelease versions.

Would be useful for instance to upgrade all related packages to Babel 7 alpha.

What is the expected behavior?

$ yarn upgrade-interactive --include-pre

It should then include pre-releases as well.

Contributor guide

Tech stack
javascriptnodejsshell
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsFamiliarity with Yarn codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Look at the `upgrade interactive` command implementation in `src/cli/commands/upgrade interactive.js`. Study how existing flags like ` latest` are implemented (parsing, passing to logic). The ` include pre` flag should modify the version matching logic in the package resolver. Check the tests in ` tests /commands/upgrade interactive.js` for patterns. Ensure the flag only affects display/selection, not actual installation behavior. The PR should add a boolean flag, update the resolution to include pre releases, and add test coverage.