Error: Cannot find module 'babel/register' about generator-node

[arthurvr]

Fixed. Thanks.

[nfriedly]

Whoot, nice turnaround time!

[SBoudrias]

Released as 1.2.1

[nfriedly]

Awesome!

On a vaguely related note, do you guys have any thoughts on adding an option to output ES5 javascript for publishing on npm and such? I know it isn't too difficult to set up, but I was a bit surprised when I realized that it wasn't built-in to the default generator-node setup. (Or is there a flag to turn it on that I just missed?)

[arthurvr]

@nfriedly It's optional. Just use --no-babel if you don't want babel.

[nfriedly]

Yea, that's what I ended up doing, but I was asking about an option that lets me write es6/7 but automatically generates es5 (in out/ maybe) and sets that up to be published to npm? So, more of a --with-debabeling sort of option.

[SBoudrias]

@arthurvr is Babel activated by default? I think we should do simple es5 by default as es6-7 is a harder publishing process.

[arthurvr]

@SBoudrias Yes. I like that, personally. That's what we plan for other generators too.

[SBoudrias]

@arthurvr could you look what the current case is for generator-node and send a PR fixing it if it's an issue?

[arthurvr]

@SBoudrias What do mean with "the current case"? The publishing process? Or the fact that Babel is on by default?

[SBoudrias]

@arthurvr Let me rephrase: can you send a PR making babel an option who's not the default?

[arthurvr]

Yes I can, though, why? That's not the approach we're taking with other generators. It's future-proof, doesn't complicate the build more than a simple gulp task and I think it's a good idea to promote using ES6.

[robbbz]

Why would anybody possible mind more features, in a backwards compatible way? As said in the other generator by silvenon as well, I don't think it should even be optional.

[SBoudrias]

Well, speaking for myself here, I still develop in ES5 and I don't intend to start using babel by default anytime soon.

Maybe it's only my opinion, but the overhead of setting up babel is usually not worth the syntactic sugar it provide me.

ES5 is working fine, I don't see why we should be eager to integrate more tooling.