util.inspect(new CompressionStream()) returns undefined

[ehmicky]

Version

v21.7.1

Platform

Linux my-laptop 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 5 21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

stream/web

What steps will reproduce the bug?

const stream = new CompressionStream('gzip');
console.log(stream); // undefined

This applies to DecompressionStream() as well.

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

Earlier Node.js versions show the same behavior.

The behavior is the same regardless of whether it is accessed as a global variable or as an import from stream/web.

The behavior happens on my machine, but it appears on other users that tried it too. I also tried it on an online REPL for Node.js.

What is the expected behavior? Why is that the expected behavior?

The return value should not be undefined.

What do you see instead?

The return value is undefined.

Additional information

I tried it in Firefox and Chrome, and it does not return undefined.

When calling CompressionStream.toString(), it appears the correct source code is being used. That source code looks normal to me.

What I find very strange is how new ... can return undefined. I through it was impossible. Even if the constructor returned a value (which it does not here), that value is ignored if it is undefined.

[KhafraDev]

node/lib/internal/webstreams/compression.js

Line 81 in 29de7f8

customInspect(depth, options, 'CompressionStream', {

node/lib/internal/webstreams/compression.js

Line 131 in 29de7f8

customInspect(depth, options, 'DecompressionStream', {

These lines are missing a return.

[ehmicky]

Right, this is it!
So new CompressionStream() and new DecompressionStream() do not return undefined. They are just printed as undefined by util.inspect().

[mertcanaltin]

I opened a pr for this place thank you very much for the details

[ehmicky]

Thanks @mertcanaltin!

[mnik7044]

hey @ehmicky is this issue resolved? Or do you want someone to work on it? I would be more than happy to help and get started.

[ehmicky]

This is being worked on at #52283

[mnik7044]

Understood, can you refer any good first issues for me, to get started with the project. I have a strong foundation of JavaScript and want to contribute to nodejs. Though all the good first issues are either resolved or someone else is working on it

[ehmicky]

@mnik7044 That's great. However, you should probably open a new issue, since this question is unrelated.