Skip to content

Conversation

@watilde
Copy link

@watilde watilde commented Jun 1, 2017

@watilde watilde force-pushed the feature/use-class branch 2 times, most recently from dafb868 to 4ced4cd Compare June 1, 2017 12:19
@watilde
Copy link
Author

watilde commented Jun 1, 2017

Wow @iarna 's patch would be better than mine to support old nodejs if it works ;)

Will close this when she makes PR. Thanks.

Oops nvm. It didn't work, unfortunately: #6

@watilde
Copy link
Author

watilde commented Jun 1, 2017

Hmm... TBH, I don't want to drop supporting v6 since it's still active as LTS: https://github.com/nodejs/LTS#lts-schedule1. I will think about the other solution.

@watilde watilde closed this Jun 1, 2017
@watilde watilde deleted the feature/use-class branch June 1, 2017 12:26
@biofractal
Copy link

Would it be possible for you to publish this change to your npm package please?

@watilde
Copy link
Author

watilde commented Jun 1, 2017

@biofractal To fix the issue and keep the backwards compatibility, we need to wait for a patch in the upstream. Once nodejs/node#13370 gets merge, let's try to update again.

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

Successfully merging this pull request may close these issues.

2 participants