Drop older Node.js versions
kibertoad opened this issue · 5 comments
Considering that there is a plan to do breaking version change for #51, it might be a good time to think about which Node.js version is preferable to support going forward. At the very least subset could be reduced to what express.js is using (super-conservative pragmatic minimum), but maybe we can bump to v4 or v6?..
@dougwilson Comments appreciated :)
I still use this in libs that support Node.js 0.8. Unless there is some specific benefit to drop support, then I think that is pointless. What are the specific benefits dropping support would achieve?
For an example, Node 0.6 is taking insane 5 mins to have all tests pass, which none other Node versions do. Can we at least drop that one?
Yea, that sounds like a concrete benefit 👍 I only use down to 0.8 at this point, so it wouldn't affect me downstream anyway. Typically I would run a report to look at the public packages that depend on this one as well to better understand, but apparently I cannot do this right now due to https://blog.npmjs.org/post/173939360180/couchdb-browse-views-unavailable
PR #56 merged now 👍