yarnpkg/yarn

workspace run commands only when it exists

Open

#6739 opened on Nov 29, 2018

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

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

Tech stack
javascriptnodejsshell
Domain
clitooling
Issue type
feature
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.
half day
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.
mostly clear
Prerequisites
Node.jsYarn workspace commands
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The 1.x line is frozen; contributions should target yarn berry. The issue requests modifying the workspace run command to skip packages without the specified command, as per the linked RFC and comments. Examine the existing implementation in the CLI plugin and implement logic to filter packages that have the command. No open PRs exist, so this is a fresh feature request for berry.