See if Node 18 introducing a new FormData global could be of any use

[TomasHubelbauer]

https://nodejs.org/en/blog/announcements/v18-release-announce/

Once the Workers runtime runs on Node 18, presumably CloudFlare will either switch to Node's fetch or alias it to their current implementation. Depending on which they do, this repository could become obsolete.

[akoidan]

This is weird, I swear to God I ran the code below on CF worker and it worked:

  let body = await request.formData();
  let file = await body.get('file');
  let fileData = await file.arrayBuffer();

fileData was a type of ArrayBuffer. Then I recreated my worker and I get into the issue described in this repo. Either they randomly run their workers on different node versions (which would be really weird) either it's configurable somewhere and I missed it.

Full code:

const html = `
 <FORM action="/upload_file" method="post">
    <input type="file" name="file"/>
    <INPUT type="submit" value="Send"> <INPUT type="reset">
    </P>
 </FORM>`

async function ulpoadUrlAndReturnResponse(request, env) {
  let body = await request.formData();
  let file = await body.get('file');
  console.log(typeof file)
  let fileData = await file.arrayBuffer();
  return new Response(typeof fileData, {
    headers: {
      "content-type": "text/plain",
    },
  });
}

export default {
  async fetch(request, env) {
    if (request.method === 'POST') {
      return ulpoadUrlAndReturnResponse(request, env)
    } else {
      return new Response(html, {
        headers: {
          "content-type": "text/html;charset=UTF-8",
        },
      });
    }
  },
};

[TomasHubelbauer]

@akoidan Do you have this flag on in both cases you describe? https://developers.cloudflare.com/workers/platform/compatibility-dates/#formdata-parsing-supports-file

[akoidan]

Thank you, I should have specified compatibilityDate, this flag is enabled by default. It's weird that w/o specified compatibilityDate, it's defaulted to some old piece of Node version. 👎