Iso dating quotall times are gmtquot
This profile defines a few date/time formats, likely to satisfy most requirements.The International Standard for the representation of dates and times is ISO 8601.When you see a data field with text like 2007-07-05 you are probably looking at a date in ISO 8601 date format.Year, month, day: YYYY-MM-DD IS 8601 is in an international standard which gives several standard syntaxes for representing Gregorian dates and times.ISO 8601 describes a large number of date/time formats.
Add five hours to that to get to UTC, and it is July 6, which is what appears to be logging, so in short, I don't see anything wrong. It does some extension/monkey patching of moment that may cause unusual behavior.
This document is a NOTE made available by the W3 Consortium for discussion only.
This indicates no endorsement of its content, nor that the Consortium has, is, or will be allocating any resources to the issues addressed by the NOTE.
Also the first shows the moment object with a cst timezone and not it's utc time. I was expecting and thought that sinze the iso standard states that Z means no timezone that it would default to utc. I'm creating a new discussion for a different question :s is because even though you may be parsing a UTC 0 string, you may want to display the moment in the users timezone.
So if you did moment.utc('2012-12-14T.276Z') or moment('2012-12-14T.276Z'), both would be treated as utc and the utc flag would be set to true. This is a pretty common use case, as it's a good practice to store times as ISO8601 UTC 0 strings on the backend and display them on the frontend in the user's timezone.