Alex Indigo
Alex Indigo
True. Sorry for the confusion. Unfortunately I don't see an easy way to change the behavior without introducing breaking changes. For your specific use case though, I'd recommend to augment...
Trying to think of a way to do it without creating breaking change. So if you have ideas – please tell :)
@wldcordeiro thanks for bringing it up. FormData doesn't use request or any other transport library. It's main job is to generate stream of data in the shape of multipart/form-data that...
Do you mind to elaborate on how it break node-fetch? And when there is no known content-length, I'm not sure how it could set Content-Length header.
:+1: Looks like a plan
Like `global.FormData` on library level? And great job on bringing libraries closer together (but not too close to keep it PG) :) Thanks.
Main purpose of this module is to allow form submission from the server-side. Exposing global variables by default would be very unexpected by majority of consumers. But I see your...
New module would behave exactly as the original one plus global export which is specified in the name. And good readme file would always help. Only confusion I can see...
Btw, I found interesting thing: ``` Note: To be clear, the difference between FormData.set() and FormData.append() is that if the specified key does already exist, FormData.set() will overwrite the existing...
As for form parsing, I think it should be different module as well. Maybe we'd expose more guts from FormData for other module to be able to use it in...