Dangerously support ES2015 import/export syntax
I know this is a somewhat controversial one, as there is no intent to transpile ES2015 import/export to CommonJS (env vs language). Saying that, I think it's worth while catering for those users on Node who can't use a bundler like Rollup/Webpack 2 to take care of import/export syntax. I don't think we should say that this is a "wise" choice, but Bublé has some pretty damn good USPs as it goes (performance, code output and far less dependencies to install).
Personally I'm finding it frustrating to register Bublé in a Node v6 project to then have to use CommonJS's require
all over the show, knowing that in a few months I'll have to "upgrade" all the requires to import/exports given Node v6 already supports pretty much all of ES2015. I'm sure others have had this issue too.
What if we were to put this feature behind a dangerous
flag/config setting so that we'd cater for those users until Node finally gets support? Ideally, we want people to use Bublé because it's awesome and we don't want there to be friction in choosing Bublé over Babel – as this probably the most important feature introduced in ES2015.
There are edge cases with transpiling ES2015 imports/exports to CommonJS but it's easy to clearly define this to users, i.e. require('foo').default
is needed when mixing the different approaches.
What are people's thoughts on this?