ramsey / composer-repl Goto Github PK

The upstream Psysh project has implemented support for version 6.x of Symfony Console, so it would be advantageous to have support for version 6.x of Symfony Process in this project.

In my experience thus far with the 6.x upgrade, this should only represent a change in explicitly providing function argument types and return types, though that may also result in a change in the minimum supported PHP version.

OK I had a look at the repro case from https://github.com/ramsey/composer-plugin-issue

The root cause of the problem really is

A workaround is to make sure everything which may clash gets loaded beforehand, e.g this appears to resolve it:

        class_exists('Symfony\Component\Console\Input\ArrayInput');

        /** @psalm-suppress UnresolvableInclude */
        require $vendorDir . '/autoload.php';

The only proper and definitive fix however would be to stop sharing the process space between the project deps and Composer.. And for that having a binary like vendor/bin/composer-repl or whatever you wanna call it which does locate the vendor dir, include autoloader, do whatever is needed, then start psysh, would be more appropriate.

You could even run vendor/bin/composer-repl as a new process (make sure to run with TTY enabled) from within the ReplCommand so that you retain BC and retain a way to call this via composer repl. But people could also add "scripts": {"repl": "@php vendor/bin/composer-repl"} and be able to call composer repl then which would run the composer-repl binary.. and that would not require a composer plugin or command integration here.

If any of the above is unclear please ask I'm happy to explain in more details.