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.

Sign up for GitHub

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

Jump to bottom

Decide supported node versions #4

Closed
jwoudenberg opened this issue Mar 6, 2016 · 2 comments
Closed

Decide supported node versions #4

jwoudenberg opened this issue Mar 6, 2016 · 2 comments
Milestone
v1.0.0

Comments

@jwoudenberg
Copy link
Collaborator

At the moment, the library is written in node v4. Is this ok or should we support lower?

If we support lower, do we write the source in ES5 or use a compilation step?

Personally, I dislike writing functional JS without having at least arrows to work with, so I'd be against supporting node 0.x with ES5 source code.
@jwoudenberg jwoudenberg added this to the v1.0.0 milestone Mar 6, 2016
@jwoudenberg jwoudenberg mentioned this issue Mar 6, 2016
Closed
6 tasks
@stoeffel
Copy link
Collaborator

stoeffel commented Mar 6, 2016

I'm vote for supporting node >=4 and against transpiling. I'm actually a little tired of babel at the moment.

@jwoudenberg
Copy link
Collaborator Author

Sounds good to me. Transpilation does involve setting up quite some infrastructure for development, deployment, CI, etc. Ok, let's considered this closed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
2 participants
@stoeffel @jwoudenberg