yarnpkg/yarn

yarn install --production does an engine check on devDependencies

Open

#5,796 opened on May 7, 2018

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

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?

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

Research direction
Investigate the install logic in the codebase to find where engine checks are performed and why they are applied to devDependencies when production is used. Look at the flag handling and dependency filtering.
Tech stack
nodejsjavascript
Domain
clidevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70