Just want to chip in here regarding the boilerplate and what to do if you prefer - like we do - to create meteor agnostic npm packages now. Since we’re on npm, we can not only provide ES2015.
@benjamn made some crucial points (see below) about how npm packages should look like to transition to true ES2015 import / export statements. Since npm is currently split between ES5 and ES6 he basically advocates the jsnext property inside a package.json to provide both the ES2015 and transpiled ES5 js entry points: Checkout the jsnext-skeleton boilerplate
He gave a talk in November (video below) about this issue in which he pleas to publish both source files and (if you care about npm) transpiled js routed via the ‘jsnext’ property (slide 71+)
I personally like the skeleton very very much - untying everything in a npm package from meteor. @arunoda what do you think? Maybe you can include this alternative in your medium post / faq section?
