yarnpkg/yarn

workspace run commands only when it exists

Open

#6,739 opened on Nov 29, 2018

View on GitHub
 (8 comments) (20 reactions) (0 assignees)JavaScript (2,731 forks)batch import
cat-featuregood first issuehelp wanted

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? feature

What is the current behavior? As specified in RFC yarn workspaces run <command> will fail if the command is missing in any package.

What is the expected behavior? I'd like yarn to execute the command only on packages that have it. That would allow each package to opt-in by just declaring the desired commands. Note that this is how lerna does it by default.

Please mention your node.js, yarn and operating system version. node v8.11.3 yarn 1.12.3 osx 10.13.6

Contributor guide

Research direction
Look at the current `yarn workspaces run` implementation in the codebase (likely in `src/cli/commands/workspace.js`). Understand how it iterates over packages and fails on missing commands. Implement a flag like ` ignore missing` or change default behavior to skip packages without the command, similar to lerna's default. Update tests accordingly.
Tech stack
javascript
Domain
cli
Issue type
Feature
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70