@alubbe hmm... What are we going to do with this pull request? I think it's a great idea to merge it but there is a lot of conflicts currently

I've rebased the PR, fixed all conflicts and reverted to using the previous version of babel-polyfill, so that we're fully backwards compatible. Let me know what you guys think, I'd love to merge it! (And then we can start refactoring the tests to use async/await)

Also, as I reported via my issue, travis no longer runs any tests - does anyone know why?
You'll have to check out this branch locally and run the tests there to verify that everything is green (it is on my machine)

Tests are green: https://travis-ci.org/exceljs/exceljs/builds/574842008

I'd be fine with bumping the version, but in that case let's remove a lot of old leftovers:

• Bump @babel-polyfill version
• Replace the current entry with their ES6 version
• ... other stuff?

So in short, it would be great to see this PR merged, and then let's spend a little time cleaning up more stuff, and then bump the version.
So maybe let's merge the TypeScript PRs, bump v1 and then merge this PR?

Do we have anyone who feels comfortable merging the TS PRs? To me that's the only thing outstanding to merge this PR and get started on the next major version.

@alubbe I've merged this and all the TS PRs I could see. Are there any I've missed?
I'd like to clean up the whole PromiseLib mess before bumping the version then we can move forwards from there :-)

@alubbe @Siemienik @coldhiber
Hi Guys - I'm thinking it might be time for yet another major change - this time to refactor the published artefacts...

The Main NPM artefact (what you get when you require/import 'exceljs' would come from the lib folder (we would probably want to bump engines directive to ">=8")

To maintain support for those that still need ES5 in node we will babel into dist/exceljs.es5.js and dist/exceljs.es5.min.js

Does anyone still use browserify ? If so we can keep them too but my thoughts are that modern web devs using react and angular (et al) can use the node type imports

What do you think?

Yes please! This was the main reason I introduced the modern files and I agree, they should be the default now.

Keeping the es5 build is nice, but we might also be fine completely dropping it, I don't think that developers that manipulate excel files via JS targeting old browsers will not be aware of transpilation.

@alubbe I've done the refactor and tidied up all of the tests and pushed to master
"verquire" in the specs is promoted to a global now and will switch on the EXCEL_BUILD env to pull in lib/ or dist/es5/ code.

I think keeping the es5 still has value - it's still likely that there are builds out there where selectively including dependencies in the transpilation might be problematic.

I feel the same is true with the browserify export. I know modern web dev is now overwhelmingy react, angular (and similar) and looking at google trends comparing webpack with browserify mirrors this, but once again - there will be builds out there still relying on the browserify export.

Given that there's practically next to no cost in keeping them, I think we might as well

I'm going to leave these changes in master for a bit, I'd like to test it out as a github dependency to check it's all ok...

Just saw that you released 3.0.0, looks great - let's wait for feedback from usage in the real world ;)