@outofcontrol@ramsey The crux of the problem is that two different versions of the same library can't be loaded into the same PHP process at once. Seems like this should be a solvable problem in terms of Composer allowing the installation of multiple versions and the autoloader erroring out if it attempts to load more than one version into the same process?
@elazar@ramsey I am very naive on composer things, but, would having an environment trigger be useful here? Having a dev, testing, staging, production etc versions for autoloading?
@heiglandreas I know. It just gets a little complicated: I integrated PHPUnit directly in a REPL, so you can write assertions directly from the terminal.
@ramsey If it was the node.js ecosystem, you might do it, but you would have 6 different versions of nikic/php-parser installed, as well as at least 4 different versions of many other dependencies 🙃
@ramsey I'm sure you absolutely know this, but just mentioning that installing PHPUnit and/or Psalm with composer as project dependencies is generally not the best.
If possible, tools like this are better installed as PHAR package, or using tools like bamarni/composer-bin-plugin.
@ramsey is there any reason to install them locally to the proiect? I install them globally as phar archives. I switched to this approach years ago specifically to fix issues like this
Add comment