bun-types 1.3.2-canary.20251105T140650 → 1.3.2-canary.20251106T140813

package/docs/api/streams.md

@@ -1,230 +0,0 @@
-Streams are an important abstraction for working with binary data without loading it all into memory at once. They are commonly used for reading and writing files, sending and receiving network requests, and processing large amounts of data.
-
-Bun implements the Web APIs [`ReadableStream`](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream) and [`WritableStream`](https://developer.mozilla.org/en-US/docs/Web/API/WritableStream).
-
-{% callout %}
-Bun also implements the `node:stream` module, including [`Readable`](https://nodejs.org/api/stream.html#stream_readable_streams), [`Writable`](https://nodejs.org/api/stream.html#stream_writable_streams), and [`Duplex`](https://nodejs.org/api/stream.html#stream_duplex_and_transform_streams). For complete documentation, refer to the [Node.js docs](https://nodejs.org/api/stream.html).
-{% /callout %}
-
-To create a simple `ReadableStream`:
-
-```ts
-const stream = new ReadableStream({
-  start(controller) {
-    controller.enqueue("hello");
-    controller.enqueue("world");
-    controller.close();
-  },
-});
-```
-
-The contents of a `ReadableStream` can be read chunk-by-chunk with `for await` syntax.
-
-```ts
-for await (const chunk of stream) {
-  console.log(chunk);
-  // => "hello"
-  // => "world"
-}
-```
-
-`ReadableStream` also provides convenience methods for consuming the entire stream:
-
-```ts
-const stream = new ReadableStream({
-  start(controller) {
-    controller.enqueue("hello world");
-    controller.close();
-  },
-});
-
-const data = await stream.text(); // => "hello world"
-// Also available: .json(), .bytes(), .blob()
-```
-
-## Direct `ReadableStream`
-
-Bun implements an optimized version of `ReadableStream` that avoid unnecessary data copying & queue management logic. With a traditional `ReadableStream`, chunks of data are _enqueued_. Each chunk is copied into a queue, where it sits until the stream is ready to send more data.
-
-```ts
-const stream = new ReadableStream({
-  start(controller) {
-    controller.enqueue("hello");
-    controller.enqueue("world");
-    controller.close();
-  },
-});
-```
-
-With a direct `ReadableStream`, chunks of data are written directly to the stream. No queueing happens, and there's no need to clone the chunk data into memory. The `controller` API is updated to reflect this; instead of `.enqueue()` you call `.write`.
-
-```ts
-const stream = new ReadableStream({
-  type: "direct",
-  pull(controller) {
-    controller.write("hello");
-    controller.write("world");
-  },
-});
-```
-
-When using a direct `ReadableStream`, all chunk queueing is handled by the destination. The consumer of the stream receives exactly what is passed to `controller.write()`, without any encoding or modification.
-
-## Async generator streams
-
-Bun also supports async generator functions as a source for `Response` and `Request`. This is an easy way to create a `ReadableStream` that fetches data from an asynchronous source.
-
-```ts
-const response = new Response(
-  (async function* () {
-    yield "hello";
-    yield "world";
-  })(),
-);
-
-await response.text(); // "helloworld"
-```
-
-You can also use `[Symbol.asyncIterator]` directly.
-
-```ts
-const response = new Response({
-  [Symbol.asyncIterator]: async function* () {
-    yield "hello";
-    yield "world";
-  },
-});
-
-await response.text(); // "helloworld"
-```
-
-If you need more granular control over the stream, `yield` will return the direct ReadableStream controller.
-
-```ts
-const response = new Response({
-  [Symbol.asyncIterator]: async function* () {
-    const controller = yield "hello";
-    await controller.end();
-  },
-});
-
-await response.text(); // "hello"
-```
-
-## `Bun.ArrayBufferSink`
-
-The `Bun.ArrayBufferSink` class is a fast incremental writer for constructing an `ArrayBuffer` of unknown size.
-
-```ts
-const sink = new Bun.ArrayBufferSink();
-
-sink.write("h");
-sink.write("e");
-sink.write("l");
-sink.write("l");
-sink.write("o");
-
-sink.end();
-// ArrayBuffer(5) [ 104, 101, 108, 108, 111 ]
-```
-
-To instead retrieve the data as a `Uint8Array`, pass the `asUint8Array` option to the `start` method.
-
-```ts-diff
-const sink = new Bun.ArrayBufferSink();
-sink.start({
-+ asUint8Array: true
-});
-
-sink.write("h");
-sink.write("e");
-sink.write("l");
-sink.write("l");
-sink.write("o");
-
-sink.end();
-// Uint8Array(5) [ 104, 101, 108, 108, 111 ]
-```
-
-The `.write()` method supports strings, typed arrays, `ArrayBuffer`, and `SharedArrayBuffer`.
-
-```ts
-sink.write("h");
-sink.write(new Uint8Array([101, 108]));
-sink.write(Buffer.from("lo").buffer);
-
-sink.end();
-```
-
-Once `.end()` is called, no more data can be written to the `ArrayBufferSink`. However, in the context of buffering a stream, it's useful to continuously write data and periodically `.flush()` the contents (say, into a `WriteableStream`). To support this, pass `stream: true` to the constructor.
-
-```ts
-const sink = new Bun.ArrayBufferSink();
-sink.start({
-  stream: true,
-});
-
-sink.write("h");
-sink.write("e");
-sink.write("l");
-sink.flush();
-// ArrayBuffer(5) [ 104, 101, 108 ]
-
-sink.write("l");
-sink.write("o");
-sink.flush();
-// ArrayBuffer(5) [ 108, 111 ]
-```
-
-The `.flush()` method returns the buffered data as an `ArrayBuffer` (or `Uint8Array` if `asUint8Array: true`) and clears internal buffer.
-
-To manually set the size of the internal buffer in bytes, pass a value for `highWaterMark`:
-
-```ts
-const sink = new Bun.ArrayBufferSink();
-sink.start({
-  highWaterMark: 1024 * 1024, // 1 MB
-});
-```
-
-{% details summary="Reference" %}
-
-```ts
-/**
- * Fast incremental writer that becomes an `ArrayBuffer` on end().
- */
-export class ArrayBufferSink {
-  constructor();
-
-  start(options?: {
-    asUint8Array?: boolean;
-    /**
-     * Preallocate an internal buffer of this size
-     * This can significantly improve performance when the chunk size is small
-     */
-    highWaterMark?: number;
-    /**
-     * On {@link ArrayBufferSink.flush}, return the written data as a `Uint8Array`.
-     * Writes will restart from the beginning of the buffer.
-     */
-    stream?: boolean;
-  }): void;
-
-  write(
-    chunk: string | ArrayBufferView | ArrayBuffer | SharedArrayBuffer,
-  ): number;
-  /**
-   * Flush the internal buffer
-   *
-   * If {@link ArrayBufferSink.start} was passed a `stream` option, this will return a `ArrayBuffer`
-   * If {@link ArrayBufferSink.start} was passed a `stream` option and `asUint8Array`, this will return a `Uint8Array`
-   * Otherwise, this will return the number of bytes written since the last flush
-   *
-   * This API might change later to separate Uint8ArraySink and ArrayBufferSink
-   */
-  flush(): number | Uint8Array<ArrayBuffer> | ArrayBuffer;
-  end(): ArrayBuffer | Uint8Array<ArrayBuffer>;
-}
-```
-
-{% /details %}

package/docs/api/tcp.md

@@ -1,221 +0,0 @@
-Use Bun's native TCP API to implement performance sensitive systems like database clients, game servers, or anything that needs to communicate over TCP (instead of HTTP). This is a low-level API intended for library authors and for advanced use cases.
-
-## Start a server (`Bun.listen()`)
-
-To start a TCP server with `Bun.listen`:
-
-```ts
-Bun.listen({
-  hostname: "localhost",
-  port: 8080,
-  socket: {
-    data(socket, data) {}, // message received from client
-    open(socket) {}, // socket opened
-    close(socket, error) {}, // socket closed
-    drain(socket) {}, // socket ready for more data
-    error(socket, error) {}, // error handler
-  },
-});
-```
-
-{% details summary="An API designed for speed" %}
-
-In Bun, a set of handlers are declared once per server instead of assigning callbacks to each socket, as with Node.js `EventEmitters` or the web-standard `WebSocket` API.
-
-```ts
-Bun.listen({
-  hostname: "localhost",
-  port: 8080,
-  socket: {
-    open(socket) {},
-    data(socket, data) {},
-    drain(socket) {},
-    close(socket, error) {},
-    error(socket, error) {},
-  },
-});
-```
-
-For performance-sensitive servers, assigning listeners to each socket can cause significant garbage collector pressure and increase memory usage. By contrast, Bun only allocates one handler function for each event and shares it among all sockets. This is a small optimization, but it adds up.
-
-{% /details %}
-
-Contextual data can be attached to a socket in the `open` handler.
-
-```ts
-type SocketData = { sessionId: string };
-
-Bun.listen<SocketData>({
-  hostname: "localhost",
-  port: 8080,
-  socket: {
-    data(socket, data) {
-      socket.write(`${socket.data.sessionId}: ack`);
-    },
-    open(socket) {
-      socket.data = { sessionId: "abcd" };
-    },
-  },
-});
-```
-
-To enable TLS, pass a `tls` object containing `key` and `cert` fields.
-
-```ts
-Bun.listen({
-  hostname: "localhost",
-  port: 8080,
-  socket: {
-    data(socket, data) {},
-  },
-  tls: {
-    // can be string, BunFile, TypedArray, Buffer, or array thereof
-    key: Bun.file("./key.pem"),
-    cert: Bun.file("./cert.pem"),
-  },
-});
-```
-
-The `key` and `cert` fields expect the _contents_ of your TLS key and certificate. This can be a string, `BunFile`, `TypedArray`, or `Buffer`.
-
-```ts
-Bun.listen({
-  // ...
-  tls: {
-    // BunFile
-    key: Bun.file("./key.pem"),
-    // Buffer
-    key: fs.readFileSync("./key.pem"),
-    // string
-    key: fs.readFileSync("./key.pem", "utf8"),
-    // array of above
-    key: [Bun.file("./key1.pem"), Bun.file("./key2.pem")],
-  },
-});
-```
-
-The result of `Bun.listen` is a server that conforms to the `TCPSocket` interface.
-
-```ts
-const server = Bun.listen({
-  /* config*/
-});
-
-// stop listening
-// parameter determines whether active connections are closed
-server.stop(true);
-
-// let Bun process exit even if server is still listening
-server.unref();
-```
-
-## Create a connection (`Bun.connect()`)
-
-Use `Bun.connect` to connect to a TCP server. Specify the server to connect to with `hostname` and `port`. TCP clients can define the same set of handlers as `Bun.listen`, plus a couple client-specific handlers.
-
-```ts
-// The client
-const socket = await Bun.connect({
-  hostname: "localhost",
-  port: 8080,
-
-  socket: {
-    data(socket, data) {},
-    open(socket) {},
-    close(socket, error) {},
-    drain(socket) {},
-    error(socket, error) {},
-
-    // client-specific handlers
-    connectError(socket, error) {}, // connection failed
-    end(socket) {}, // connection closed by server
-    timeout(socket) {}, // connection timed out
-  },
-});
-```
-
-To require TLS, specify `tls: true`.
-
-```ts
-// The client
-const socket = await Bun.connect({
-  // ... config
-  tls: true,
-});
-```
-
-## Hot reloading
-
-Both TCP servers and sockets can be hot reloaded with new handlers.
-
-{% codetabs %}
-
-```ts#Server
-const server = Bun.listen({ /* config */ })
-
-// reloads handlers for all active server-side sockets
-server.reload({
-  socket: {
-    data(){
-      // new 'data' handler
-    }
-  }
-})
-```
-
-```ts#Client
-const socket = await Bun.connect({ /* config */ })
-socket.reload({
-  data(){
-    // new 'data' handler
-  }
-})
-```
-
-{% /codetabs %}
-
-## Buffering
-
-Currently, TCP sockets in Bun do not buffer data. For performance-sensitive code, it's important to consider buffering carefully. For example, this:
-
-```ts
-socket.write("h");
-socket.write("e");
-socket.write("l");
-socket.write("l");
-socket.write("o");
-```
-
-...performs significantly worse than this:
-
-```ts
-socket.write("hello");
-```
-
-To simplify this for now, consider using Bun's `ArrayBufferSink` with the `{stream: true}` option:
-
-```ts
-import { ArrayBufferSink } from "bun";
-
-const sink = new ArrayBufferSink();
-sink.start({ stream: true, highWaterMark: 1024 });
-
-sink.write("h");
-sink.write("e");
-sink.write("l");
-sink.write("l");
-sink.write("o");
-
-queueMicrotask(() => {
-  const data = sink.flush();
-  const wrote = socket.write(data);
-  if (wrote < data.byteLength) {
-    // put it back in the sink if the socket is full
-    sink.write(data.subarray(wrote));
-  }
-});
-```
-
-{% callout %}
-**Corking** — Support for corking is planned, but in the meantime backpressure must be managed manually with the `drain` handler.
-{% /callout %}