Breaking change in 1.8.0 about form-data-encoder HOT 10 CLOSED

Ah, right, I see now. The release however mentions the change, so it was intentional: https://github.com/octet-stream/form-data-encoder/releases/tag/v1.8.0 the "Backport headers changes"

from form-data-encoder.

Sorry I broke your product. The https://github.com/octet-stream/form-data-encoder/releases/tag/v1.9.0 should revert these changes. 1.8.0 will be marked as deprecated. Thanks for reaching me out!

from form-data-encoder.

Thank you so much.

We plan on moving to v2. For now our build toolchain doesn't emit an ESM artifact but we will change this in the next few weeks - to be able to benefit from the most recent versions of your fantastic package, and some others that are also moving to ESM-only.

Again, thanks. Much appreciated.

from form-data-encoder.

I'm gonna close this, hope your issue is resolved.

from form-data-encoder.

This is rather a bug fix for #9, otherwise this method will return NaN if File without known length was discovered, so I had to make this change. In v2 it was also introduced in minor release. This is unusual change in minor, but it was necessary.

from form-data-encoder.

The commit message is "fix eslint issue". There is no mention about a bug fix. Instead it looks like a cosmetic change. Except if the commit message is misleading.

from form-data-encoder.

And anyway, this change prevents every project that depends on the library to build with the strict setting of typescript compiler. This is huge.

from form-data-encoder.

Okay, I can revert this.

from form-data-encoder.

Thanks. We have fixed the version to 1.7.2. in our own projects, for now - we have a critical product that requires to be built tonight. But it may not be as easy for some other teams. 🙂

from form-data-encoder.

Also please consider upgrade to v2 when it is possible, the 1.x will no longer receive updates (except for those things I might broke in 1.8.0)

from form-data-encoder.