Skip to content

Eliding should not happen on workspace filters with only one project matched #18453

@mio-moto

Description

@mio-moto

What is the problem this feature would solve?

Eliding is a useful tool when running multiple projects in union, however it has been proven somewhat cumbersome in our case when the filter is applied to only one project. Imagine a folder structure like this:

- package.json
o webapp
  - package.json
o backend
  - package.json

having a package.json in the root with scripts like

{
  "scripts": {
    "dev": "bun run --filter '*' dev",
    "dev:webapp": "bun run --filter 'webapp' dev",
    "dev:backend": "bun run --filter 'backend' dev",
  },
  "workspaces": ["backend", "webapp"]
}

causes eliding on commands like bun run dev:webapp and bun run dev:backend where it's not necessary to keep an overview of the terminal output.

(This is a [long overdue] followup to this comment: #11465 (comment))

What is the feature you are proposing to solve the problem?

This would restore regular bun run output when only one project is being run, as if it was transparently running the other projects without workspaces.

What alternatives have you considered?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliSomething to do with CLI argumentsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions