Support es6 based on the .es6 extension

[phated]

This can easily be done with https://6to5.org/usage.html#require-hook but it would register as .js also. Opening another issue to allow configuration objects to solve this.

[silkentrance]

@phated I see where this is going to. Well, for one thing, node-interpret does not require the external modules, node-rechoir does. It will require the module, say require("6to5/register"). This in turn will return a function R, that when called will expect the user to provide a configuration object.

This function will then be passed on, as the module parameter, to whatever registration function is defined for the module '6to5/register'.

In there, you would want your configuration object to be passed to function R.

[tkellen]

@phated could you weigh in here? i don't have a problem with what @silkentrance has proposed but i'm also not going to be the one implementing es6 support (at least not for the next few weeks). @silkentrance, could you implement what you're thinking for on 6to5?

[silkentrance]

@phated, @tkellen

I have created a patch for both node-interpret and test cases for node-rechoir.

Check out vibejs/node-rechoir@8ec6edcd210b144eebc108138b19df0491256475

Please note that this version of node-rechoir expects you to pass in the requiring module, see gulpjs/rechoir#10 for more information.

[phated]

@tkellen what are your thoughts on letting 6to5 register on .js if it is loaded, but only load on .es6? e.g. if your gulpfile is named gulpfile.es6 then 6to5 will be required and hook into .js and .es6 so you don't need to name all your files .es6

[tkellen]

👍

[phated]

Added tests in rechoir for es6 - gulpjs/rechoir@e80518c