yarnpkg/yarn

yarn should warn if a resolution appears to attempt to change a top level dependency

Open

#7,320 opened on 2019年6月5日

GitHub で見る
 (18 comments) (0 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-featuregood first issue

説明

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

What is the current behavior? Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

  1. install a package with any version, e.g "pkg": "^1.0.0"
  2. add resolutions field in package.json, pkg: "1.0.0"
  3. update "pkg": "^1.0.0" to "pkg": "^2.0.0" in deps
  4. run yarn why pkg

It only displays "pkg": "^2.0.0" being used, but no info about pkg: "1.0.0", while in yarn.lock, can find pkg: "1.0.0" related info

What is the expected behavior? expect to display resolutions package info as well

Please mention your node.js, yarn and operating system version. yarn: 1.16.0 macOS node: 8.16.0

コントリビューターガイド

技術スタック
javascriptnodejs
領域
clitooling
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Understanding of Yarn's resolution algorithmFamiliarity with yarn why commandNode.js development setup
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
This issue requests that `yarn why` also display packages specified in the `resolutions` field of package.json. The 1.x line of Yarn is frozen; new features are being developed on Yarn Berry (https://github.com/yarnpkg/berry). To implement this, you would need to examine the resolution logic in the Yarn 1.x codebase, likely in files related to package resolution and the `why` command (e.g., `src/package resolver.js` or `src/cli/commands/why.js`). The community discussion (18 comments) may provide additional context on expected behavior and edge cases. Note that a fix for this feature should consider the frozen status and potentially be submitted to the Berry repository instead.