[Feature Proposal] Native Support for Server-Sent Events (SSE)

[Naghal]

Description
I would like to suggest adding first-class support for Server-Sent Events (SSE) in Laravel.
Currently, Laravel provides excellent support for real-time communication through broadcasting (e.g., Pusher, Ably, WebSockets). However, there is no simple, built-in way to stream one-way events from the server to the client using the standard [EventSource API](https://developer.mozilla.org/en-US/docs/Web/API/EventSource).

SSE is a lightweight alternative to WebSockets for many real-time use cases, such as:

• Progress updates for long-running tasks
• Live logs or system monitoring dashboards
• Notifications or status updates that don’t require bi-directional communication

Why SSE?

• Native to browsers: The EventSource API is supported by most modern browsers without extra dependencies.
• Simpler than WebSockets: SSE works over standard HTTP, does not require an additional server or library, and scales well with Laravel’s existing request/response lifecycle.
• Complementary to Broadcasting: Not all apps need WebSockets; sometimes a simple one-way stream is enough.

Proposed API
A possible way to expose SSE in Laravel could be through a SseResponse (similar to StreamedResponse):

use Illuminate\Support\Facades\Response;

Route::get('/events', function () {
    return Response::sse(function ($sse) {
        foreach (range(1, 5) as $i) {
            $sse->event('progress', ['step' => $i]);
            sleep(1);
        }
    });
});

The response helper (Response::sse) could handle:

• Correct headers (Content-Type: text/event-stream, Cache-Control: no-cache)
• Flushing output as events are sent
• Automatic event formatting (id, event, data)

Example Client Usage

const source = new EventSource("/events");

source.addEventListener("progress", (e) => {
    console.log("Progress:", JSON.parse(e.data));
});

Conclusion
This feature would give Laravel developers an easy, framework-native way to use SSE without relying on manual implementations of StreamedResponse or third-party packages. It aligns with Laravel’s goal of making common web tasks elegant and expressive.