Open erwinw opened 1 year ago
While you are correct, I would argue that this an issue with our outdated support matrix. Node 12 is EOL since April 2022 (over a year ago) and I don't think we should be supporting it anymore.
Not disagreeing, just bumped into the use of the ??
due to webpack (though that is unrelated), then noticed the mismatch between the support matrix and the engine support for ??
and decided to file. Personally I totally agree with what you're suggesting.
Also, thanks for the swift response, much appreciated.
Agree. Let's bump up the support matrix
Hey, would you like me to close this issue or create a PR to update the support matrix? I guess this would also require bumping the engine
entry in the package.json, and maybe a change log entry, a major version bump, ... so not sure if & how you would like me to proceed?
@erwinw A PR altering the support matrix in that md file and changing the engine is package.json is the right thing to do.
I don't think we need a version bump:
According to the package.json Luxon supports Node v12+, but the nullish coalescing operator is used, which is not supported before Node v14.