Skip to content

Node 4 support #32

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
Closed
nkzawa opened this issue Dec 28, 2016 · 4 comments
Closed

Node 4 support #32

nkzawa opened this issue Dec 28, 2016 · 4 comments
Labels
enhancement

Comments

@nkzawa
Copy link

nkzawa commented Dec 28, 2016 •
edited
Loading

I wonder why this library supports only >=5. I think plugins should support what webpack does as much as possible.

I want Node 4 support for our library (next.js) which only this module has the problem.
@nakedible
Copy link

I concur wholeheartedly. Node 4 is still in active LTS, and for example AWS Lambda does not support anything newer.

@gajus
Copy link
Owner

gajus commented Jan 16, 2017

Please use the thumbs up on the issue to cast vote for a feature. I am using these to prioritise issues across many repositories.

@arianrhodsandlot
Copy link

arianrhodsandlot commented Jan 9, 2018 •
edited
Loading

Any good news here? Are there any codes using features in Node.js v5 which v4 doesn't have?

@chrisblossom chrisblossom mentioned this issue Apr 20, 2018
Merged
@chrisblossom
Copy link
Contributor

Node v4 support has been added as of #53. This issue can be closed.

@gajus gajus closed this as completed Apr 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nakedible @nkzawa @gajus @chrisblossom @arianrhodsandlot