[andrewstuart]

This strategy underestimates the cost and difficulty of configuration.

Hopefully the message that is coming through here is that configuring Babel is extremely hard and time consuming and error prone and is a massive, massive headache.

I am still right now trying to work out why async and await do not work after spending all day on it.

Probably for Babel experts configuration is easy and quick but for those who are not specialists in it forcing users down a configuration path is deeply, excruciatingly painful.

[pas]

They need a big getting started page and direct newcommers to it where they don't try to be clever, but directly list scenarios.

Or they (or you) could make a configurator (they already have a build-tool focused one, but they need one kind of like what jQuery has) on the website, where you can select your target browser version(s), and what features you want enabled. Bam. Magic! Here's a JSON file, put it into your project root.

Async/await, I'd just go with TypeScript and then transpile the ES6 to ES5 with Babel.

See: https://github.com/andrenarchy/jspm-typescript-es6-boilerpla...