Question: about size option

[1Blackdiamondsc]

Impact
Node Fetch did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure.

For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

Patches
We released patched versions for both stable and beta channels:

For v2: 2.6.1
For v3: 3.0.0-beta.9

Workarounds
None, it is strongly recommended to update as soon as possible.

[jimmywarting]

Size is a node-fetch only option. we have toughs about deprecating it since we want to be more strict and follow the spec more correctly. we want node-fetch to be somewhat isomorphic so that your code can work the same across different env, node is shipping a very close to spec compatible fetch implementation in 17.5 behind a flag. so some day node-fetch will no longer stick around. and Deno have fetch built in so... there is that.

#1438

it might also be solvable in some other form later on with fetch observer and fetch events that gets triggered when making a fetch request.