Compatibility Concern: psr/http-message v1/v2 Conflict with Laravel Passport

[wikichua]

Hello,

I hope this message finds you well.

I'm currently working on a project where I'm using php-mcp/laravel alongside laravel/passport. I've encountered a dependency conflict that I believe might be related to psr/http-message versions required by these two packages.

It appears that:

laravel/passport (through league/oauth2-server) requires psr/http-message ^2.0
php-mcp/laravel (through php-mcp/server and react/http) requires psr/http-message ^1.0
This conflict prevents me from running composer update successfully.

I understand that php-mcp/laravel itself might not be the direct cause of this conflict, as it stems from its dependencies. However, I was wondering if you might have any insights or potential alternative solutions regarding this psr/http-message version discrepancy, especially as react/http is a dependency.

Perhaps there's a recommended way to handle such conflicts in projects integrating php-mcp/laravel with packages like laravel/passport, or if there's a plan to update underlying dependencies to support psr/http-message ^2.0 in the future.

Thank you for your time and any guidance you can provide.

Best regards,

[CodeWithKyrian]

This is actually a known issue that I'm currently working on in the base php-mcp/server package. You can track the progress and discussion on this specific conflict at php-mcp/server#23.

For now, I'd recommend tracking the issue at that link since any resolution will need to happen at the server package level first, then trickle down to this Laravel integration. I'm actively investigating potential workarounds and will update the issue as I make progress.

If you have any insights or alternative approaches you'd like to suggest, feel free to comment on that issue. I always appreciate community input on these kinds of ecosystem challenges!