Laravel + websockets: Unhandled promise rejection with TypeError about http HOT 1 CLOSED

Hey @ryanbaldisco, thanks for bringing this up 👍

You're seeing this message because of our Promise v3 release back in July of 2023 last year. I don't think this is a bug in our HTTP component, seems more like something that should be reported in https://github.com/beyondcode/laravel-websockets, as they're throwing an error where only exceptions are allowed for our error events. Although I'm not sure how relevant this currently is, as the project has been archived on 2024-02-07. Laravel reverb seems to be the suggested replacement for this, which also builds on top of ReactPHP.

We could use a Throwable to support both exceptions and errors, as #506 also suggests, but this doesn't work with older PHP versions and will ultimately be a BC break. For v1 we're still supporting these older PHP versions, which will change with ReactPHP v3 (PHP 7.1+). With v3, we want to improve error reporting anyways, so this might be a thing of the past once the next major version is released.

I believe this should answer your question, so I will close this ticket for now. We can reopen this if we can actually prove that this is a bug in this component. If you do need to reopen the ticket, please provide any new findings 👍

from http.