"Cloning streams in Node.js's fetch() implementation is harder than it looks. When you clone a request or response body, you're calling tee() - which splits a single stream into two branches that both need to be consumed. If one consumer reads faster than the other, data buffers unbounded in memory waiting for the slow branch. If you don't properly consume both branches, the underlying connection leaks. The coordination required between two readers sharing one source makes it easy to accidentally break the original request or exhaust connection pools. It's a simple API call with complex underlying mechanics that are difficult to get right." - Matteo Collina, Ph.D. - Platformatic Co-Founder & CTO, Node.js Technical Steering Committee Chair
代码里最“不明觉厉”的部分来了：
，推荐阅读WPS官方版本下载获取更多信息
Instruct Codex to optimize benchmarks to 60% of runtime，这一点在WPS下载最新地址中也有详细论述
Read the full story at The Verge.