Repository navigation
Different timestamp created by node.js and browser #9805
Description
Activity
Could you please give an example of Node.js and browser output, to show what you think is wrong?
the node one is 07:xx:xx
but browser is 15:xx:xx
Those are the same date, just displayed differently. The
Zin2016-11-26T07:41:09.319Zstands for UTC+0, and you’re in UTC+8.You can check this by using
new Date().toString()andnew Date().toJSON(): Both of these will return the same value in Node.js and your browser.Reacted by Przemek Nowickisorry about that,another stupid question.
Reacted by haffedali and Lalit Sekhar Behera@EasonWang01 Don’t worry about it, I’m glad I could help!
@Pustur #4318 was the PR that changed that, you can follow the links/discussion there. Tbh, I find it a bit weird that the ISO representation is used as the more “human-readable” format (which is what
util.inspectis supposed to show), but I am pretty sure you could have endless arguments about that. :)Reacted by Loris Bettazza@EasonWang01 > sorry about that,another stupid question.
Not stupid at all! I was just thinking the world was upside down when I saw it logged to different formats! I'm happy I found your question, it was really educational for me
new Date() function create different timestamp for nodejs runtime, the browser created is correct,what might cause this problem?