Skip to content

Doesn't work with the latest reactPHP promise v.3.2 #22

Closed

Description

@gidzr

When installing with composer:

composer require clue/shell-react:^0.2

Get this response from composer:

Problem 1
- Root composer.json requires clue/shell-react ^0.2 -> satisfiable by clue/shell-react[v0.2.0].
- clue/shell-react v0.2.0 requires react/promise ~1.0|~2.0 -> found react/promise[v1.0.0, ..., v1.3.0, v2.0.0, ..., v2.11.0] but it conflicts with your root composer.json require (3.2.0).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

I can see this is an older project but your docs page mentions v8 php, so I thought it might have been upgrade with the latest reactPHP.

I'd like to test out this reactPHP shell.. because I've been struggling to get a live interactive shell using the hello world examples for https://reactphp.org/child-process/ .. ie. that when I create a terminal for mysql, python, or other shell terminal, I've been looking to create a non-blocking client to that terminal, that I can use. But instead the IO is blocked because this kind of terminal doesn't provide a return signal back to the childprocess.

I was hoping your reactPHP shell might provide the solution for this situation.

Activity

  1. PaulRotmann commented on Aug 4, 2025

    @PaulRotmann
    Collaborator

    Thanks for reporting this! You're right that the current released version (v0.2.0 from 2015) only supports react/promise v1-2, but we've actually already added support for react/promise v3 in PR #21. This issue is already resolved in the codebase, but we haven't released v0.3.0 yet.

    The v0.3.0 release is planned and includes this Promise v3 compatibility along with several other improvements. However, we're still finalizing a few additional features for this milestone before cutting the release.

    For now, you can use the latest development version from the main branch if you need Promise v3 support immediately. Otherwise, the official v0.3.0 release will include this fix when it's ready.

    Closing this issue as it's already been addressed. Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions