CJS ESM modules 
I am greatful that you spend your time to develop this library and that you made it available for free.


But as an author of such a popular widely used library you are also responsible to main the project in a way that people can rely on it.
The decisions to migrate to ESM modules without a working backup option is pretty narrow minded.

1. NPM stats clearly show that the usage of this library continuously decreases because of these ongoing import issues
2. Many project owners who work with different setups simply can not or are not allowed to change their development environments. In some companies there are rules what you are allowed to change, and such a change triggers a huge overload in the QA department
3. Changing project setups to fit a single library will probably break other libraries

We use nestjs and I know about the ESM import issue there, but nestjs is a huge framework and bigger companies simply won't rely on home made frameworks. Their rather set in proven technology stacks.

As of now this library is unusable with nestjs and we have to use graphql-upload-minimal.

In my opinion you should clearly focus on compatibility otherwise the effort you have put in here will be in vain.