This time, its different. The transpilers are build-time polyfills that fill the gap of current browser/server implementation and the newest JS/CSS specs.
Transpilers trans-compile Javascript and CSS to current workable version, so developers could be more productive with JS/CSS latest features and transpilers would translate them into current supported version of code.
From my opinion the most useful es6 feature is arrow functions (=>) which comes from coffeescript. This syntax sugar bind the this value automatically, so developer wont forgot the binding anymore.
The original code is
(function() {
‘use strict’;
document.addEventListener(‘DocumentLocalized’, function() {
}.bind(this));
}());
We can use arrow function to replace function() {}.bind(this)
to () => {}
(function() {
‘use strict’;
document.addEventListener(‘DocumentLocalized’, () => {
});
}());
Currently the arrow functions only default enabled on Firefox. So developer could not use this directly on their project. With babel javascript transpiler the js could be translated to current workable version automatically.
(function() {
‘use strict’;
document.addEventListener(‘DocumentLocalized’, function() {
});
}());
The transpiler will know the content does not need 'this' reference and skip the binding. Note the Javascript transpiler still stick into vanilla javascript. It does not invent new syntax, but it make new specs could be used or experiment in current environment.
From CSS perspective, CSS variables brings variables into CSS. Pre-define some color and use everywhere on project is possible.
The origin style is
a {
color: #847AD1;
}
pre {
padding: 10px;
}
It's frustrated when the stylesheets expand larger and we need to change the new color or size everywhere.
We can use CSS variables to predefine the changeable stuff into pseudo ':root' element.
:root {
–maincolor: #847AD1;
–size: 10px;
}
a {
color: var(–maincolor);
}
pre {
padding: var(–size);
}
Looks good. But the same situation occurred. Currently the CSS variables only support on Firefox. So developer could not use this directly on their project. With myth CSS transpiler the CSS could be translated to current workable version automatically.
a {
color: #847AD1;
}
pre {
padding: 10px;
}
Note the CSS transpiler still stick into CSS specs. It does not invent new syntaxes like LESS or SASS does. It just make new CSS specs could be used or experiment in current environment.
Besides the feature polyfill, running transpiler before deploy also help developer catch out the error since transpiler will traverse the source and parsing syntaxes. Transpiler will bark you when any error in your source.
You may wonder setup an environment with above JS/CSS transpiler seems take some time. webapplate 2.3.0 already integrated with babel and myth grunt tasks to auto transpile your JS/CSS code to current workable version. webapplate jshint/githook also support es6 syntax validation (yes the .jshintrc is exactly borrowed from gaia project), so your project is future proved and keep maintainable.