Tim Neutkens

@blakeembrey sorry for bumping this issue. Just noticed the deprecation notice added to the readme here on github is not on [npm](https://www.npmjs.com/package/tsd) which could lead to people still using it...

Cool, then it's fine 👍

It seems like this pull-request at least partially solves some of the issues users are having in #416, we got some reports from Next.js users too (Next.js now uses hard-source-webpack-plugin...

We should document the "why is it any" here given that it's not a bug. The body can be anything provided by the user so in general you need to...

Will keep this open so that we can document it 👍

@HaNdTriX any reason for not updating the built-in type?

Hey, so far we've spent over 10 hours trying to reproduce this and we can't find a problem with Next.js as-is. Please provide a reproduction so that we can continue...

> have you troubleshot this both with esmExternal set to false and true ? With it enabled there is no memory leak, memory usage does not increase. It's likely something...

Investigated this one on my flight back from Next.js Conf, it's a known issue with cloning responses of `fetch()` in node-fetch and I could reproduce it with standalone node-fetch as...

@alexparish React duplication is fixed in #42252 out on 13.0.1!