-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to ES6 / ES2015? #9
Comments
Hi! I am not familiar with the status of ES6 on nodejs, are there any benefits (especially in performance)? |
@markusn Using native ES2015 functions instead of your own will always be faster e.g. |
It seems interesting as it is possible to transpile to ES5 for backward compatibility for users of older versions of node. However I will not likely have time to implement this in the near future, but would happily take a pull-request. |
did a pull request, see #12 |
@markusn, were you thinking of a build step and traspiling down to ES5? I'm down to help migrate to ES6+ |
Hi! I'm going to do a 2.0.0 with ES6 (no transpiling to ES5). |
Awesome! Let me know if there's anything I can do to help. I've already changed |
Any news here? I'd love to use this in a client-side JS modules only project. I can help port too. |
Hi! What is stopping you from using it at the moment? |
@markusn browsers don't support Common JS, and I'm not using a bundler. |
@justinfagnani I have a PR open to solve this: #22 . Would that work for you? |
fixed in v1.4.0 |
What do you think about migrating the project to ES2015?
The text was updated successfully, but these errors were encountered: