Closed Yshayy closed 9 years ago
Yep. I think it's also safe to use ES2016 features, at least those in stage > 1 (mainly async and rest/spread properties - https://github.com/tc39/ecma262).
It's a fairly small lib and it's already written. What would we gain from converting to ES2015/16? This would force users to transpile if they're using it on the client side.
I thought might be adding a dist folder and making the transpiled file the entry point (like in coffescript project?).
But that's a valid point, the project won't improve much if using ES2015/ES2016, and it will add a bit overhead.
So, Closing issue.
You mean convert to ES2015?