fix(package.json) Explicit drop support for node<18 #59
Conversation
Followup to pillarjs#54: That PR added a statement that support for node<18 is dropped, and amended the CI accordingly. This PR builds on that and makes this support statement explicit in the package.json.
|
I knew someone would see this and open this PR. I did this intentionally. We are in a process of fixing nearly 10 years of stagnation and are attempting to make the most smooth transition we can for consumers. Since we did not introduce any changes that actually BREAK those versions I have chosen to not change the engines field. This means that we are a bit more free to steward folks forward without putting in arbitrarily roadblocks in the upgrade path. That said, we do not intend to ship fixes for anything other that security issues to support node versions older than 18. We are working on docs and stuff for this, but it takes time and we are focused on getting the code released and stable first. So, happy to hear your opinion on this, because I anticipated it being controversial. |
|
Egg on my face! I was not aware this was intentional - #54 didn't mention it, and I thought it was just an oversight. |
|
No apologies necessary! I was quite concerned this decision would be seen as the wrong way and I didn't want to cause more confusion by trying to preemptively explain my thinking in case it was never going to become an issue for folks. In open source it is sometimes hard to tell what folks will care about and what they will not even notice, and with the workload we have taken on trying to get these packages unstuck, I was trying to optimize for maintainer time over correctness. |
Followup to #54:
That PR added a statement that support for node<18 is dropped, and amended the CI accordingly.
This PR builds on that and makes this support statement explicit in the package.json.