Skip to content
This repository has been archived by the owner on Jun 15, 2020. It is now read-only.

Don't use babel-preset-es2015 (or maybe drop babel completely?) #104

Open
typeofweb opened this issue May 2, 2016 · 3 comments
Open

Don't use babel-preset-es2015 (or maybe drop babel completely?) #104

typeofweb opened this issue May 2, 2016 · 3 comments

Comments

@typeofweb
Copy link

Use babel-preset-es2015-node4 instead of babel-preset-es2015

Since this generator's package.json specifies required nodejs version as 4.2.6, there's no need to use babel-preset-es2015. ES2015 babel preset makes babel transpile all the codebase from ES2015 into ES5 even though node.js 4 can understand parts of ES2015 syntax. Therefore babel-preset-es2015-node4 could be used instead to make the development process even faster.

Alternative: Require nodejs 6 and drop babel completely

Nodejs v6 supports over 92% of ES2015 (according to node.green). If you agree to require nodejs v6 then there's no need to have babel as a dependency anymore. Nodejs v6 becomes active Long Time Support version in October 2016.

@dsebastien
Copy link
Owner

Well the main target of the generator are Web browsers. I'm not sure we can already forget about ES5 (?)

@typeofweb
Copy link
Author

Yes, but as far as I understand the codebase, Babel is not used for client-side code. It's only used to transpile gulpfile, isn't it?

@dsebastien
Copy link
Owner

I get your point, you're right as far as the build of the generator itself is concerned; the same is true for the build of the modern-web-dev-build project :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants