yarnpkg/yarn

Yarn --production tries to resolve devDeps as well

Open

#3,630 opened on 2017年6月13日

GitHub で見る
 (55 comments) (48 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-featurehelp wantedneeds-discussiontriaged

説明

Do you want to request a feature or report a bug? This is a bug, or unexpected behaviour.

What is the current behavior?

  1. Have a package.json which have devDependencies and one of them are private
  2. Run yarn --production
  3. Yarn tries to resolve all packages and fails, because have no access to private packages

To fix that I need additional workaround with authToken (the problem arises in docker build process).

What is the expected behavior? Yarn should only resolve production packages when --production flag exposed.

Please mention your node.js, yarn and operating system version.

node -v
v8.1.0
yarn --version
0.24.6

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

技術スタック
javascriptnodejs
領域
clibuild system
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Basic Yarn CLI usageUnderstanding of devDependencies vs dependencies
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
15
調査方針
Review the yarn 1.x codebase, specifically the resolver module that handles production flag (likely in src/resolvers/). Examine the logic that resolves dependencies and ensure devDependencies are skipped when production is set. Check the comments in the issue for any proposed fixes or workarounds. Note that the yarn 1.x repository is frozen; the fix may need to be ported to the berry (yarn 2.x) repository at https://github.com/yarnpkg/berry.