yarnpkg/yarn

`yarn add pkg` should default to the version used in the other workspaces instead of latest

Open

#4,154 opened on Aug 11, 2017

View on GitHub
 (9 comments) (1 reaction) (0 assignees)JavaScript (2,731 forks)batch import
cat-featuregood first issuehelp wantedhigh-prioritytriaged

Repository metrics

Stars
 (41,514 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

This is an enhancement.

What is the current behavior?

Running yarn add pkg in a workspace will install the latest version of pkg.

What is the expected behavior?

Running yarn add pkg in a workspace should use the same version as the other workspaces if possible in order to deduplicate them.

This is a potentially confusing change so we can discuss it there.

Contributor guide

Research direction
Investigate the `yarn add` command's version resolution logic and identify how the version of an existing package in other workspaces can be extracted. Then modify the resolver to prefer that version over the latest remote version.
Tech stack
javascriptnodejs
Domain
cli
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
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60