/proc/self/task/20/root/node24/lib/node_modules/npm/node_modules/undici/docs/docs/api
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
# EventSource > ⚠️ Warning: the EventSource API is experimental. Undici exposes a WHATWG spec-compliant implementation of [EventSource](https://developer.mozilla.org/en-US/docs/Web/API/EventSource)for [Server-Sent Events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events). ## Instantiating EventSource Undici exports a EventSource class. You can instantiate the EventSource asfollows: ```mjsimport { EventSource } from 'undici' const eventSource = new EventSource('http://localhost:3000')eventSource.onmessage = (event) => { console.log(event.data)}``` ## Using a custom Dispatcher undici allows you to set your own Dispatcher in the EventSource constructor. An example which allows you to modify the request headers is: ```mjsimport { EventSource, Agent } from 'undici' class CustomHeaderAgent extends Agent { dispatch (opts) { opts.headers['x-custom-header'] = 'hello world' return super.dispatch(...arguments) }} const eventSource = new EventSource('http://localhost:3000', { dispatcher: new CustomHeaderAgent()}) ``` More information about the EventSource API can be found on[MDN](https://developer.mozilla.org/en-US/docs/Web/API/EventSource).