Skip to content
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

Port to ES6 (via Babel.js) #151

Open
aseemk opened this issue Feb 18, 2015 · 4 comments
Open

Port to ES6 (via Babel.js) #151

aseemk opened this issue Feb 18, 2015 · 4 comments

Comments

@aseemk
Copy link
Member

aseemk commented Feb 18, 2015

Writing this lib in CoffeeScript has provided a big productivity and robustness boost, but we could probably get those same benefits with ES6 now — along with broader approachability and appeal.

https://babeljs.io/
https://babeljs.io/docs/learn-es6/

We might not be able to port the tests from CoffeeScript yet, assuming we still want to use Streamline (that provides an even bigger productivity and robustness boost when writing tests), until Streamline implements support for Babel too — which is on its roadmap.

Sage/streamlinejs#254

@aseemk aseemk added this to the v2 redesign milestone Feb 18, 2015
@zcei
Copy link

zcei commented Sep 10, 2015

Just found this lib as I started working with neo4j, and I heavily +1 for porting to ES6!
CoffeScript was nice as long as ES5 was around, but at latest with the release of node.js v4.0 you have a lot similarity.

For rewriting streamline stuff, I suggest using async / await, which is in Stage 2 and thus enabled by default in Babel (ref.)

@hilkeheremans
Copy link

+1 as well, not necessarily because it's ES6 but because it's no longer coffeescript and will open the door to more pull requests (especially from my end, eg for #164 :-)).

@eldarshamukhamedov
Copy link

+1. CoffeeScript is a significant hurdle to get past for wanna-be contributors. The Neo4j driver landscape is full of abandoned and poorly-written code, but v2 of this repo seems very promising. CS is the only reservation I have when considering its use in production.

@adamdilek
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants