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

What language spec can be used for contributing? #35

Open
genrym opened this issue Aug 16, 2017 · 1 comment
Open

What language spec can be used for contributing? #35

genrym opened this issue Aug 16, 2017 · 1 comment

Comments

@genrym
Copy link

genrym commented Aug 16, 2017

Can I use ES6 features?

@samcday
Copy link
Owner

samcday commented Sep 2, 2017

Hey @genrym - I haven't touched this package in a while, but the .travis.yml build matrix still checks that things work as far back as node 0.10, which definitely doesn't support any ES6 features ;)

That said, if you're interested in contributing, maybe the first thing you could look at is getting Babel in here? I'm perfectly okay with the code being ES6 if we have a npm prepare step that compiled the ES6 down to ES5. That said, I don't want this package to then string along a whole runtime, so we'd still be limited in what language features we can use (no generators for example).

Alternatively, I wonder if there's any way to get stats on who is using this package nowadays. If the majority (read: >60%) was on Node 5.0 or higher, I'd be happy to drop support for the older runtimes and target language features available in Node 5 and higher.

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

No branches or pull requests

2 participants