Re:The cost of transpiling ES2015 in 2016
by brokentone on Monday February 08, 2016 @11:05AM
(#11058825)
Not necessarily. You could build multiple targets and dynamically serve one over the other. Not as hard as it sounds.
[ Parent
| on HN ]
Re:The cost of transpiling ES2015 in 2016
by frandroid on Monday February 08, 2016 @12:09PM
(#11059331)
Isn't that what the parent said?
Re:The cost of transpiling ES2015 in 2016
by brokentone on Tuesday February 09, 2016 @02:41PM
(#11068142)
Didn't when I posted it
What tools do you use to make it happen?
Re:The cost of transpiling ES2015 in 2016
by brokentone on Tuesday February 09, 2016 @02:44PM
(#11068168)
Still working it through. The steps as I see it:
Figure out which browsers to support on which features: https://kangax.github.io/compat-table/es6/
Have an alternate .babelrc with a transpile blacklist that points to a separate dest
Build a regex to match those browsers in your CDN (I use Fastly). Vary on the value you create.
Point said browsers asking for the normal JS payload to the alternate dest.