Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

Standalone usage will need RemoteEvent anyway as this component is used to represent the payload of the webhook (request parsers are about building RemoteEvent objects).

For usage out of Symfony of the client part of the component (i.e. receiving webhooks), you would have to implement the equivalent of the WebhookController for your framework, deciding how you want to process parsed events (which should be asynchronous because most servers expects a fast response from clients to accept the webhook, which is why the core implementation uses Messenger).

For usage out of Symfony of the server part, there is 2 options:

• if your project uses Messenger, you can use that part in the same way than in a Symfony project (dispatching a SendWebhookMessage in the bus), once you register the SendWebhookHandler as a messenger handler in your messenger setup
• otherwise, you can use the TransportInterface directly in whatever way fits your project

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

Hello? This issue is about to be closed if nobody replies.

Hello? This issue is about to be closed if nobody replies.

Not quite resolved, but I assume there are no further plans to improve stand-alone re-use

Closing as this is indeed not actionable right now. Feel free to ask for reopening if you want to discuss an idea that makes it easier to use standalone, or submit a PR directly. Thanks