What can cause `new Date()` to return incorrect dates?

#javascript #mongodb #help

I am trying to solve a problem in which I have found date values in my MongoDB database to be inaccurate.

For example, in my database, I have a list of tokens that are set to be deleted by the database 12 hours after they're created. I noticed some of my tokens were missing so I disabled the expiration function. It turns out some of these tokens have inaccurate creation dates. The worst case was a token that was created on June 25th but has an creation date value of '2020-06-03T09:00:29.506+00:00'. That's a 22 day difference!

I use JavaScript's new Date() method to create the dates. MongoDB by default will convert a date object created by JavaScript's new Date() to UTC.

I have ensured my system's built-in time synchronization is activated. What else can I do to make new Date() return correct dates?

Top comments (2)

Soumya Ghosh Dastidar • Jun 26 '20

I don't exactly know what's wrong with your code without seeing it completely. Just some tips :

Always set the Date on the server and not from the client side.
Use unix timestamp for easier calculations, they can be easily converted to any date-time format.

Nisa JThani • Jun 26 '20

Thank you for your reply.

The Date is already set on my Node.js LoopBack 4 server
I haven't tried this method. I will do this next. Thanks.

DEV Community

What can cause `new Date()` to return incorrect dates?

Top comments (2)

Read next

Step-by-Step Guide to an Angular Expandable and Collapsible Sidebar with Icons

A 50+ pages reactjs PDF cheat sheet with code examples of 30+ topics

TypeScript Traps: Top 10 Mistakes Developers Make and How to Dodge Them

Building React Native In-App Modules bypassing the JS bridge.