hmm, that true

but, a lot of our users still uses node v8 - we should think about how to care about them :)
or give some months to adapting their environments

Okay let's try a totally different approach then :)
I propose to move node v8 support to ES5 imports - users of the old version will get a clear message of what they need to change and everyone on node v10 and newer will get the full power and speed of newer features such as async iteration.

This is strictly speaking a semver-incompatible change, but I think the upgrade path is simple enough - what do you think?

@guyonroche what's your take on supporting outdated versions of node? How often would you like to release a new major version of exceljs?

I've also restored testing v8 on travis, so now that node v8 is a first class citizen as it is right now and the only breaking change is that users of node v8 will get a message to change their require statement. Can we merge that and publish it as 4.0.0 @guyonroche ? Then I can finish my work on async iteration and stream cancellation

We have to publish v3.8.3 from current master first - 3.8.2 has bug inside - #1179 #1180 #1178

WIP because, 3.8.2 doesn't work now, we have to publish 3.8.3 version before v4.

I've resolved all merge conflicts and have added testing for node 14