0

I am working on one of my client issue. I have changed my system timezone to "(UTC-5:00) Eastern time (US & canada)". I wrote below code in my project -

new Date(year,month.date)

I observed that if month value is 0 or 1 ,then it is working fine -

new Date(2021,1,21)
Sun Feb 21 2021 00:00:00 GMT-0500 (Eastern Standard Time)

but if month value is greater than 1, then timezone is getting change by 1 hour-

new Date(2021,2,21)
Sun Mar 21 2021 00:00:00 GMT-0400 (Eastern Daylight Time)

which is causing problem. please someone suggest on this that why it is happening and what might be solution of this. expected answer should be in javascript or angular. moment library also will be accepted. this issue is only reproducible for few timezone. It is working fine for IST.

Shikha Shrivastav
  • 21
  • 5
  • 2
    That will be daylight savings that becomes active at different times around the world (if it's observed at all). Notice the difference between `GMT-0500 (Eastern Standard Time)` and `GMT-0400 (Eastern Daylight Time)` Not sure when it kicks in for US but I know it's earlier than it is here in the UK which is last Sunday in March. – phuzi Feb 17 '22 at 14:25
  • Welcome to the minefield of timezones and daylight saving. Any answer we give would probably have to be specific to any problems this expected behaviour is giving you. – phuzi Feb 17 '22 at 14:28

2 Answers2

0

your date is ticking over the EST's daylight savings time

You can get round this by specifying the timezone of your date, for example:

new Date(2021, 3, 21).toLocaleString('en-GB', { timeZone: 'UTC' }));

will return the date formatted to en-GB UTC timezone string, or you can use something like the Date.UTC function to ensure all your dates are handled as a UTC timezone

datetimes are a bit of a nightmare in JS - these might not fix your issue, but hopefully they'll point you in the right direction.

In regards to packages, if you're doing a lot of datetime work i would suggest Moment or the smaller Luxon packages, they really take a lot of the headache out of JS dates

Rhyan-WoodsAndWalker
  • 532
  • 2
  • 7
  • Re "en-US timezone": en-US is a language tag which is used by *toLocaleString* to infer a format. The US has 5 timezones with different offsets plus daylight saving in most places. – RobG Feb 17 '22 at 22:38
  • toLocaleString will return string, i need date object for further calculation- – Shikha Shrivastav Feb 20 '22 at 10:39
  • sorry it's difficult to say what youre trying to achieve from your question - i'd potentially look into using Date.UTC then, which will ensure all of your Date objects are from the same timezone eg. new Date(Date.UTC(year, month, day, hour, minute, second)); – Rhyan-WoodsAndWalker Feb 21 '22 at 12:51
0

EMCAScript uses the host system settings for timezone offset. The output ofDate.prototype.toString is based on those settings and inferred rules for standard and daylight saving if observed.

Given one timestamp says Eastern Standard Time and the other Eastern Daylight Time, it shows that the dates relate to times when the offset rules based on your system's regional settings change from standard time to daylight saving time.

If you only want standard time, there should be an option in your regional settings to turn off observing daylight saving. But that will be a system wide setting and will potentially affect the displayed dates and times everywhere on your system.

Alternatively, you can use toLocaleString with a location that is in the US EST timezone but doesn't observe daylight saving, e.g. America/Panama. However, the format is different to that of the default toString. If you want the same format, you'll have to construct it yourself, see How to format a JavaScript date

console.log(new Date(2022,1,25).toLocaleString('en',{timeZone:'America/Panama', timeZoneName:'short'}));

Note that this has no effect on the Date instance itself, it only changes the values displayed when toLocaleString is called this way.

RobG
  • 142,382
  • 31
  • 172
  • 209