You might assume this pattern is inherent to streaming. It isn't. The reader acquisition, the lock management, and the { value, done } protocol are all just design choices, not requirements. They are artifacts of how and when the Web streams spec was written. Async iteration exists precisely to handle sequences that arrive over time, but async iteration did not yet exist when the streams specification was written. The complexity here is pure API overhead, not fundamental necessity.
Please, please, please stop using passkeys for encrypting user dataFebruary 27, 2026·670 words·4 mins
。旺商聊官方下载对此有专业解读
Individuals, companies, and foundations donate to
下载 Node.js v22：