This would be a breaking change. Unfortunately mime-types v3 did not update their engines declaration when dropping compat for older node versions.

Hi @ljharb , what would be the right path for form-data to benefit from the newest mime types then ? Is there an action I can take ?

Unfortunately the best approach there would be for mime-types v2 to backport those changes, or for v3 to restore engines.node support.

Tell me if I am wrong but as I can see it, the engines.node has been updated 8 days ago. Long after my PR. mime-type did not even produce a new version since this change. So maybe a solution would be to pin your dependency to mime-type to "3.0.1", removing the caret.

What do you think ?

(NB: I check stuff on my mobile from holidays, so it's not handy and I may have missed something, sorry if that's the case)