therootcompany / tz.js Goto Github PK

This is packing a few files that npm doesn't need and making it look bigger than it really is.

Either of these would work:

xtzDate.toDate = function () {
  return new Date(xtzDate.toISOString());
};

xtzDate.toDate = function () {
  return new Date(xtzDate.year, xtzDate.month, xtzDate.date, xtzDate.hour, xtzDate.minute, xtzDate.second, xtzDate.millisecond);
};

I see that toUTC returns an object. I find this preferable to the way other libraries do it because then I can build out the format I need. However, I don't have all the pieces I really want.

Would it be better for the object to contain all the formats of the various date parts according to the unicode symbols? Intl.DateTimeFormat().resolvedOptions().timeZone;

datetime-local does not accept a format that the Date object can provide, and does not give a format that the Date object understands...

• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local
• https://developer.mozilla.org/en-US/docs/Web/HTML/Date_and_time_formats

<input type="datetime-local"></input>

The datetime-local requires the value in the format YYYY-MM-DDThh:mm[:ss[.sss]]. For this use case it would be nice to be able to do XTZ.toUTC(new date()).toISOString() or XTZ.toISOLocaleString(new Date())... or something

function (x, tz = new Intl.DateTimeFormat().resolvedOptions().timeZone) {
  // ...
}

Also, the name toUTC may be misleading... it's more like toUTCOffset or toISOOffset.

See https://tc39.es/proposal-temporal/docs/

In particular, if we use similar language, we can use the same diagram, which is very helpful!