11–20 of 31 posts
There's also this one https://github.com/mping/5to6
Yes, And it's 3 days younger than xto6. It does not support function/prototype => classes. And also it is trying to encourage people to convert their ES5 codes into ES6 but it's implemented in ES5 itself !
Interesting idea, but the backwards compatibility of ES6 means that you can refactor a project piece by piece as you work on it - IMO that's a better approach.
Sure, but even just as a learning exercise it's fun to pass ES5 code through it, particularly for people not familiar with the new features in ES6. It could definitely do with a list of supported/unsupported functionality.
Earlier quoted context omitted.
Yes, And it's 3 days younger than xto6. It does not support function/prototype => classes. And also it is trying to encourage people to convert their ES5 codes into ES6 but it's implemented in ES5 itself !
Don't take it as an attack, it's always better to have more choices and approaches to learn from, nobody is trying to diminish your work.
Earlier quoted context omitted.
Yes, And it's 3 days younger than xto6. It does not support function/prototype => classes. And also it is trying to encourage people to convert their ES5 codes into ES6 but it's implemented in ES5 itself !
Don't take it as an attack, it's always better to have more choices and approaches to learn from, nobody is trying to diminish your work.
I am asking as a poor JS developer - what are the benefits of this newer style?