Distributing ES6

[goatslacker]

section on how to publish es6 files to npm

[fredericksilva]

Stackoverflow answer

The pattern I have seen so far is to keep the es6 files in a src directory and build your stuff in npm's prepublish to the lib directory.

You will need an .npmignore file, similar to .gitignore but ignoring src instead of lib. José F. Romaniello

[ljharb]

The "main" entry point should always be ES5, and node-style commonJS. Original source files and babel settings should be included in the published packages, along with tests.

We definitely should add a section about this.

[andykenward]

Check out the issue on redux. I've seen npm packages compile babel+es6 code to es6 into a \es or\es6 folder. And refer to it in the package.json as "jsnext:main"

So it could possible be used for tree shaking with rollup or webpack2