As explained in the commit message, the one catch is that Atom should not automatically transpile all files that end in
.js, as that could be wasteful/confusing for packages that are not expecting to be transpiled. In the current version of the PR, I just went with the convention that everything in an
atom-es directory will get transpiled. That’s obviously a limiting directory structure, and is naive as it excludes tests. Now I’m thinking that the
package.json should enumerate globs or paths that should get transpiled instead so you can structure your package however you like.
An alternative is to require a special file extension (possibly
.es for ECMAScript?) and transpile based on that, but I don’t think that would play well with other tools in the real world that expect
Either way, please share your thoughts on the pull request.