Writer cannot cope with ArrayBuffer

Version

v19.0.0-pre

Platform

Darwin

Subsystem

web/streams

What steps will reproduce the bug?

Try the following code both on chrome & nodejs:

const str = "H4sIAAAAAAAAE0vLzwcAIWVzjAMAAAA=";
const buf = Uint8Array.from(atob(str), c => c.charCodeAt(0));
const ds = new DecompressionStream("gzip");
const writer = ds.writable.getWriter();
writer.write(buf.buffer);
writer.close();
await new Response(ds.readable).arrayBuffer();

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

No response

What do you see instead?

node:internal/errors:477
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of ArrayBuffer
    at new NodeError (node:internal/errors:388:5)
    at _write (node:internal/streams/writable:315:13)
    at Writable.write (node:internal/streams/writable:337:10)
    at Object.write (node:internal/webstreams/adapters:166:63)
    at ensureIsPromise (node:internal/webstreams/util:172:19)
    at writableStreamDefaultControllerProcessWrite (node:internal/webstreams/writablestream:1091:5)
    at writableStreamDefaultControllerAdvanceQueueIfNeeded (node:internal/webstreams/writablestream:1206:5)
    at node:internal/webstreams/writablestream:1278:7 {
  code: 'ERR_INVALID_ARG_TYPE'
}

Additional information

No response

@ronag

For this issue is the function write supposed to work on Buffer | Uint8Array | ArrayBuffer?
cc @ronag @VoltrexKeyva

According to the documentation, the function write is not supposed to work on <ArrayBuffer> in node.(It works in chrome.)

writer.write(buf);

Using <Uint8Array> is fine.

So, this can be closed?

For this issue is the function write supposed to work on Buffer | Uint8Array | ArrayBuffer?

So, this can be closed?

No, CompressionStream and DecompressionStream are supposed to handle BufferSource, that means, as per how this is done WebCryptoAPI - <ArrayBuffer> | <TypedArray> | <DataView> | <Buffer> should all be valid chunks.

The WPTs for this will soon be enabled #50631.

I'd like to work on this issue if no one is currently working on it.

I can investigate the BufferSource handling in CompressionStream / DecompressionStream and put together a PR with a regression test.

stream: accept ArrayBuffer in CompressionStream and DecompressionStream

Navigation Menu

Repository navigation

`Writer` cannot cope with `ArrayBuffer` #43433

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Writer cannot cope with ArrayBuffer #43433

Description

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

Activity

debadree25 commented on Dec 21, 2022

MarybethGasman commented on Feb 1, 2023

MrJithil commented on Oct 9, 2023

panva commented on Nov 9, 2023

suuuuuuminnnnnn commented on Feb 21, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`Writer` cannot cope with `ArrayBuffer` #43433