yarnpkg/yarn

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

Open

#4154 opened on Aug 11, 2017

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

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

Tech stack
javascriptnodejs
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.
3-5 days
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.
mostly clear
Prerequisites
Understanding of Yarn workspacesJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Research the current behavior of `yarn add` in workspace context, particularly the version resolution logic. Focus on the `src/cli/commands/add.js` and related resolver files. Review the discussion in the issue comments for desired behavior and edge cases. Consider how to detect version conflicts between workspaces.