Investigate register-babel necessity

[jamesplease]

I accidentally discovered that I no longer needed to manually register Babel, given that gulpfile.babel.js seemed to register it for me, so I removed that from the code in b404c5f.

Shortly after, I decided to update the generator-babel-boilerplate with this change, but @thejameskyle pointed out that it may not be intended to work that way (babel/generator-babel-boilerplate#240 (comment)).

This issue to get to the bottom of this!

[jmm]

I'm pretty sure that's how they intend it to work: gulpjs/gulp#830 (comment). (And off the top of my head I'm not sure if / how you could make it work otherwise.) BTW there's a broken link in your post.

[jamesplease]

Thanks for doing that research for me, @jmm! It makes sense that it would work this way. I'm going to do a liiiittle more research before I close this, but it seems to pretty much be all cleared up.

Thanks again! Oh, and I fixed that link ;)

[jmm]

Thanks! Fortunately I remembered that discussion and just had to skim it again to confirm. It's tricky because of the lack of support for multiple file extensions, and I don't know if it's even possible to invoke babel-register multiple times with different settings (though maybe this pirates thing would enable that?), and even if you could do that the support for gulpfile.babel.js isn't based on sub-gulpfiles having any specific directory organization or naming scheme to identify them.