yarnpkg/yarn

yarn install --production does an engine check on devDependencies

Open

#5796 opened on May 7, 2018

View on GitHub
 (4 comments) (0 reactions) (1 assignee)JavaScript (41,514 stars) (2,731 forks)batch import
cat-buggood first issue

Description

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

bug

What is the current behavior? yarn install --production does an engine check on devDependencies

What is the expected behavior? yarn install --production should not do an engine check on devDependencies

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

Contributor guide

Tech stack
javascriptnodejs
Domain
clitooling
Issue type
bug
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.
1-3 hours
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.jsYarn internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the engine check logic in the install command files, such as src/cli/commands/install.js. Understand how devDependencies are filtered during production install and why the engine check is applied to them. Check the relevant test files for expectations.