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.
Relative time shows `in 0 seconds`
See original GitHub issueRelative time shows in 0 seconds for “now” dates. Instead it should display: ‘Just now’
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:8 (3 by maintainers)
Top Results From Across the Web
How to make moment.js show relative time in seconds?
You can get seconds between two moment objects using diff specifing 'seconds' unit as second parameter: var mom = moment("20170703 00:00:00" ...
Read more >Solved: Getting a Relative Time Indicator to Display ZERO
If the indicator is RELATIVE time, shouldn't a value of ZERO seconds be 00:00:00? It should. My first guess was that you're converting...
Read more >Displaying Relative Time - BlackWasp
In this article we will create a reusable class to generate the text for such time offsets with times expressed in units of...
Read more >Use a relative time slicer or filter in Power BI - Microsoft Learn
For example, you can use the relative time slicer to show only video views within the last minute or hour.
Read more >datetime — Basic date and time types — Python 3.11.1 ...
While date and time arithmetic is supported, the focus of the implementation ... class datetime.timedelta(days=0, seconds=0, microseconds=0, milliseconds=0 ...
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
@UziTech no, the list of issues is the only tool I have to manage the things I actually can fix, and I’m arguably not even able to keep up with that. I can’t have a big list of tickets sitting around waiting for browsers to update.
If luxon is going to use the Intl API and not try to work around some of its shortcomings then it should at least keep issues like this open until it is resolved in the API so it has a better chance of being found by anyone who needs a work around.