Partially revert "stream: reduce internal usage of public require of util"

[addaleax]

This partially reverts commit c97851d.

Streams code should ideally require on public APIs as much as possible,
because it is exported as readable-stream.

Refs: #26698
Refs: nodejs/readable-stream#416

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[bmeck]

I'm unclear as to what this accomplishes exactly and the support it is providing.

[addaleax]

@bmeck It should make maintaining readable-stream easier, and it makes the fallback code in lib/streams.js make any sense at all (in its current form, the internal require would always throw in userland, rendering the rest of the try/catch useless).

If that isn’t an acceptable reason for this PR in your eyes, please close it, as I don’t think it’s worth spending much time arguing about this relatively minor change.

[targos]

@addaleax I don't exactly understand how this works, because the code in lib/stream.js is not part of the readable-stream module

[bmeck]

@addaleax I think thats fine, just please add a disclaimer somewhere to that effect in the actual file itself to prevent some thrashing we are seeing on moving things between internal/public APIs. I would like to PR removing code for various fallback types like process.binding as we move forward with LTS cycle when we have purely public APIs we haven't deprecated though, but thats a different PR.

[addaleax]

Hm right, it looks like the fallback code in streams.js might not be used by readable-stream at all … in that case we can probably remove it altogether? Can somebody from @nodejs/streams confirm?

[mcollina]

Yes, it’s not used in the active line. You can remove it.