Closed qntm closed 1 year ago
There will be no leap second at the end of June 2023, so the plan above simplifies to:
t-a-i@4
will appear, and support for t-a-i@3
will be dropped.t-a-i@3
, only t-a-i@4
.t-a-i@4
will recognise it, not t-a-i@3
.A little late, but t-a-i@4
has now been published, and t-a-i@3
is now deprecated.
t-a-i@3
, only t-a-i@4
.t-a-i@4
will recognise it, not t-a-i@3
.It has been announced that there will be no leap second at the end of December 2023. Neither t-a-i@4
nor t-a-i@3
need to recognise this. And t-a-i@3
continues to be valid and usable...
In the next major version of
t-a-i
my intention is to stop shipping CommonJS modules and start shipping ES modules instead. Ast-a-i
actually does seem to be in use, I'm not intending to make a breaking change like this arbitrarily, as I have with all my other, largely unused npm packages. Currently my plan is to wait for Node.js 14 to end Long-Term Support, at the end of April 2023. In May 2023t-a-i
will drop support for Node.js 14, which of course is a breaking change and will require a major version bump fromt-a-i@3
tot-a-i@4
, so I will take this opportunity to carry out the conversion to ES modules at the same time.As with
t-a-i@1
andt-a-i@2
, support fort-a-i@3
will be dropped oncet-a-i@4
is released. New leap seconds, if and when they are announced, will be incorporated intot-a-i@4
only. In particular,t-a-i@3
.t-a-i@4
will appear, and support fort-a-i@3
will be dropped.t-a-i@3
andt-a-i@4
will recognise it.t-a-i@3
, onlyt-a-i@4
.t-a-i@4
will recognise it, nott-a-i@3
.