You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Use
babel-preset-es2015-node4
instead ofbabel-preset-es2015
Since this generator's
package.json
specifies required nodejs version as4.2.6
, there's no need to usebabel-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. Thereforebabel-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.
The text was updated successfully, but these errors were encountered: