1 of 20
2 of 20
3 of 20
4 of 20
5 of 20
6 of 20
7 of 20
8 of 20
9 of 20
10 of 20
11 of 20
12 of 20
13 of 20
14 of 20
15 of 20
16 of 20
17 of 20
18 of 20
19 of 20
20 of 20



The WritableStreamDefaultWriter interface from the Streams API is produced by calling WritableStream.getWriter(). It locks the writer to the WritableStream, preventing any other streams from writing to the underlying destination.


WritableStreamDefaultWriter() Creates a new WritableStreamDefaultWriter object instance.

Instance properties

WritableStreamDefaultWriter.closed Allows you to write code that responds to an end to the streaming process. Returns a promise that fulfills if the stream becomes closed, or rejects if the stream errors or the writer’s lock is released.

WritableStreamDefaultWriter.desiredSize Returns the desired size required to fill the stream’s internal queue.

WritableStreamDefaultWriter.ready Returns a Promise that resolves when the desired size of the stream’s internal queue transitions from non-positive to positive, signaling that it is no longer applying backpressure.

Instance methods

WritableStreamDefaultWriter.abort() Aborts the stream, signaling that the producer can no longer successfully write to the stream and it is to be immediately moved to an error state, with any queued writes discarded.

WritableStreamDefaultWriter.close() Closes the associated writable stream.

WritableStreamDefaultWriter.releaseLock() Releases the writer’s lock on the corresponding stream. After the lock is released, the writer’s no longer active. If the associated stream is errored when the lock is released, the writer will appear errored in the same way from now on; otherwise, the writer will appear closed.

WritableStreamDefaultWriter.write Writes a passed chunk of data to a WritableStream and its underlying sink, then returns a Promise that resolves to indicate the success or failure of the write operation.


The following example shows the creation of a WritableStream with a custom sink and an API-supplied queuing strategy. It then calls a function called sendMessage(), passing the newly created stream and a string.

Inside this function it calls the stream’s getWriter() method, which returns an instance of WritableStreamDefaultWriter. A forEach() call is used to write each chunk of the string to the stream. Finally, write() and close() return promises that are processed to deal with success or failure of chunks and streams.

 const list = document.querySelector('ul');

 function sendMessage(message, writableStream) {
   // defaultWriter is of type WritableStreamDefaultWriter
   const defaultWriter = writableStream.getWriter();
   const encoder = new TextEncoder();
   const encoded = encoder.encode(message, { stream: true });
   encoded.forEach((chunk) => {
       .then(() => defaultWriter.write(chunk))
       .then(() => {
         console.log("Chunk written to sink.");
       .catch((err) => {
         console.log("Chunk error:", err);
   // Call ready again to ensure that all chunks are written
   //   before closing the writer.
     .then(() => {
     .then(() => {
       console.log("All chunks written");
     .catch((err) => {
       console.log("Stream error:", err);

 const decoder = new TextDecoder("utf-8");
 const queuingStrategy = new CountQueuingStrategy({ highWaterMark: 1 });
 let result = "";
 const writableStream = new WritableStream({
   // Implement the sink
   write(chunk) {
     return new Promise((resolve, reject) => {
       const buffer = new ArrayBuffer(1);
       const view = new Uint8Array(buffer);
       view[0] = chunk;
       const decoded = decoder.decode(view, { stream: true });
       const listItem = document.createElement('li');
       listItem.textContent = `Chunk decoded: ${decoded}`;
       result += decoded;
   close() {
     const listItem = document.createElement('li');
     listItem.textContent = `[MESSAGE RECEIVED] ${result}`;
   abort(err) {
     console.log("Sink error:", err);
 }, queuingStrategy);

 sendMessage("Hello, world.", writableStream);

For more information on WritableStreamDefaultWriter visit MDN Web Docs.

Didn’t find what you were looking for? Open a support ticket.