Hi @Elzair - thanks for this contribution. I have to admit that I'm a little hesitant when it comes to merging this, as the desired functionality can be provided in userland as well (by defining your own form.onPart = function(part) { handler).

Do you see any compelling reasons why this should be part of formidable itself?

@Elzair thanks! A bit late here, but if you still using formidable library or want similar thing check out with npm i formidable@canary - preview of v2 release.

Also, there are issues that want this feature, and if couldn't land at v2, it will be possible to the user to do whatever he want because the #545 Plugin API. Also, because the reason that v2 exports everything - all the parser classes, all the plugins, all the utils, aliases and etc.

I'm going to close this, because it's based on pretty old code base.
But I'll add you with Co-authored-by.

@all-contributors please add @Elzair for code and idea

@tunnckoCore

I've put up a pull request to add @Elzair! 🎉

Thanks everyone!