You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Can I use ES6 features?
The text was updated successfully, but these errors were encountered: