-
Notifications
You must be signed in to change notification settings - Fork 361
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
Remove node 4 and 5 support, End-Of-Life #303
Comments
I'm not sure if adding a library that was recently created and it's only tangentially used in json2csv really justifies a major version bump. I was planning to create a very simple table cli just for our use case. Wdyt? |
I'm fine either way, but I think it still stands that we shouldn't be supporting a node version that Node itself doesn't. I can actually see us doing something like |
Just give me a day or so and I'll come back with a simpler proposal for the pretty print :) Regarding deprecating node 4 and 5. I have no problem with that. But I don't see a problem keeping it until we have to change it either. After all, people still use Node 0.10 :) |
Yeah, and people still use Windows XP, doesn't mean they should haha Sounds good regarding the pretty print |
The Node org has ended support for Node 4 in April and Node 5 in 2016, so we shouldn't be supporting these. Also the new maintained cli-table3 only supports node 6+.
https://github.com/nodejs/Release/blob/643af71ee8365efbdccaa134690425ea05931279/README.md#release-schedule
The text was updated successfully, but these errors were encountered: