Nick K.

Well, in my case, I use the library alongside with next-connect, so I expect an error to be forwarded to their [onError](https://github.com/hoangvvo/next-connect#optionsonerror) callback. Not sure for other cases, but I...

I've released `[email protected]` and `[email protected]` with these fixes. Thanks @Baune8D!

@tinovyatkin What if you need to do something after the `next()` call? For example, I'm using this scenario in multipart middleware: ```js import {parse} from "then-busboy" import {unlink} from "promise-fs"...

Hey, it seems like node-fetch is going to have multipart parser soon, if [this PR](https://github.com/node-fetch/node-fetch/pull/1314) gets merged. Maybe this would be helpful for you somehow?

Hey, good catch, I have never really tested types compatibility. You're right, this method is implemented by all browsers, according to compatibility table on MDN page of this method: https://developer.mozilla.org/en-US/docs/Web/API/File/webkitRelativePath#browser_compatibility...

Tried in fresh setup with the code from [latest commit](https://github.com/octet-stream/form-data/tree/533e7675222471217dca0d8d1f71e76780c6386c) and it does seem to work now, I don't get any errors. For more input: tsconfig.json: ```json5 { "include": ["test.mjs"],...

Not sure why the error mentioned in my first comment is happening, but I assume TS falls back to `NodeJS.ReadableStream` interface, if web streams does not have `[Symbol.asyncIterator]()`. Got this...

Do you have tsconfig.json in your project? I don't see this error when I have one.

> With this config you need to add a // @ts-check comment at the top of files you want TypeScript to check. You don't if you set `checkJs` to true....

> fyi octet-stream/form-data is cjs only for now, so it can't depend on lates fetch-blob that is ESM-only. Actually, `formdata-node` is a dual module. It has both [`ESM and CJS...