abdullah/til
1
0
Fork 0
mirror of https://github.com/jbranchaud/til synced 2026-01-04 23:58:01 +00:00
Code Issues Projects Releases Wiki Activity

Add ISO-8601 Formatted Dates Are Interpreted As UTC as a javascript til

Browse Source
This commit is contained in:
jbranchaud
2017-12-04 22:10:00 -06:00
parent 1c02cc9605
commit 8d05a9a2f1
2 changed files with 30 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
javascript/iso-8601-formatted-dates-are-interpreted-as-utc.md Normal file
View File

@@ -0,0 +1,28 @@
# ISO-8601 Formatted Dates Are Interpreted As UTC
Using `new Date()` or `Date.parse()` with a string that represents a date is
a great way to create a `Date` object for a specified date. A variety of
formats are accepted by these methods.
But, caution!
There are subtle differences in how those dates will be interpreted. Given
any old string that reasonably represents a date, the date will be
interpreted using the local time zone, in my case `CST`.
```javascript
> new Date('2017-12-4')
Mon Dec 04 2017 00:00:00 GMT-0600 (CST)
```
However, as soon as we use an ISO-8601 compliant date format, ECMAScript 5
specifies that the date ought to be interpreted using the UTC time zone. As
you can see, the results are drastic enough to affect what day it comes out
to.
```javascript
> new Date('2017-12-04')
Sun Dec 03 2017 18:00:00 GMT-0600 (CST)
```
[Source](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse#ECMAScript_5_ISO-8601_format_support)