-
-
Notifications
You must be signed in to change notification settings - Fork 149
Cannot redeclare React\Promise\resolve() #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Autoloading via |
Yeah, sorry. I never saw the function loading before, but I also thought that this is the only way in the end.
The problem is, that I have the dependency defined in a dependency - I do not have control about it. I didn't track it down 100%, but in my case I have Codeception (testing-suite) installed globally, just because it is rather large and takes a while to install. Other issues might come from composer plugins, which have to be installed globally. This would be related to composer/composer#3082 ... There's already an issue about it in composer composer/composer#3003 And guzzle had something similar guzzle/guzzle#676. They solved it with an if statement ;). But for sure it would be better to have the fix in composer. |
This allows a global version of React\Promise alongside a local version. Closes #23
hey , |
@bhajan903 check your server logs, that error is so generic we can't do anything with it. Also please open a new ticket for if the error is ReactPHP related. |
Hi,
we stumbled over this issue today:
We have a composer packages installed globally and per project which both depend on
react/promise
.I think the composer autoloader always loads the file specified here which looks to me like the source of the error.
I don't know if composer should handle that...
You could wrap the definitions in a
function_exists()
call if you have to use the legacyfiles
autoloading.The text was updated successfully, but these errors were encountered: