Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Timestamps show “invalid date” in Safari+Firefox
See original GitHub issueThis is an issue I only came across in Safari:
These disappear after a reload, the generated HTML reads as follows:
<span class="relative-date" title="Invalid date" data-time="NaN" data-format="tiny">Invalid date</span>
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Invalid date in safari - javascript - Stack Overflow
This function on safari throw error with Invalid date . Solution To fix it we should use: import _format from 'date-fns/format'; ...
Read more >Fix: Invalid date on Safari & IE - LinkedIn
Here, IE returns 'NaN' and Safari returns 'Invalid Date' because for some reason, IE and Safari do not support this type of date...
Read more >RangeError: invalid date - JavaScript - MDN Web Docs
The JavaScript exception "invalid date" occurs when a string leading to an invalid date has been provided to Date or Date.parse() .
Read more >Javascript's Date() does not work with IE & Safari
Here, IE returns 'NaN' and Safari returns 'Invalid Date' because for some reason, IE and Safari do not support this type of date...
Read more >[Solved]-moment invalid date in firefox, safari-moment.js
Coding example for the question moment invalid date in firefox, ... This chart shows that only the UTC version of "YYYY-MM-DD" is supported...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello, I’m seeing this again in Firefox:
It looks like
"UTC"is getting dumped back into thepost.created_at. The times correct themselves when you refresh.Should be fixed with #23