What's the best way of handling when the server and client times differ? For example, if the clients clock is 5 mins behind, it would show 'in 5 minutes' instead of 'just now' which looks wrong.

I tried to enter a relative date like timeago('2016-06-10 12:12:12'), but after doing so it seems that the real-time updating no longer works. I believe this is because the diffSec function uses that date as the base to compare against rather than new Date().

// calculate the diff second between date to be formated an now date.
function diffSec(date, nowDate) {
  nowDate = nowDate ? toDate(nowDate) : new Date();
  return (nowDate - toDate(date)) / 1000;
}

If this isn't possible currently, perhaps if a relative date is entered, it should instead store an offset against new Date() and use that when working out the difference?

I noticed something. If I do timeago().format(new Date("2017-08-09 18:00")) (it is 2017-08-11 12:39 right now) I get 1 day ago. But in human terms, thats wrong. For me it was actually 2 days ago, even if it weren't 48 hours. If you say 1 day ago I assume that it was yesterday, not the day before late in the night.

Picky, I know. In your README.md you mentioned the possible use of a data-timeago attribute instead of the "W3C-illegal" datetime attribute (see W3C Recommendation) which we couldn't actually use before this PR. This PR adds the possibility to use the data-timeago attribute for the automatic rendering while maintaining backwards compatibility.

:walking: The v1.x.x received so many feedbacks and suggestions, so v2.0.x will do it.

v2.0.x will not compatible with v1.0.x, details below:

• [x] Read date from datetime attribute for <time datetime='xxxxx'>.
• [x] API register will be a static method, replace of an instance method.
• [x] Will use coding style of new timeago().

What else, welcome to additional. ref #12 #23 #47 #59 #61

When this library is used in components with life-cycles (e.g. react), capabilities of unregistering a single relative time instance is critical.

Current implementations have several disadvantages in such circumstances:

1. Does not support canceling timer for a singular DOM in a timeago instance. Instead all timers in the instance are cancelled. Because of this, we need to create a timeago instance for every single relative time instead of create one and share, which is really slow when there are many relative times to display (e.g. long lists).

2. Does not share member functions across timeago instances so that every timeago instance needs more memory, which makes it even worse --> Please use prototypes to eliminate the memory cost.

This PR adds the minimal interval option to refresh intto timeago.render.

This option will help developers to avoid disturbing users especially in case of having multiple sub-minute elements. An example is available at https://cl.ly/2r39322u3e23 (adapted from gitlab-org/gitlab-ce#47976).

Signed-off-by: Takuya Noguchi [email protected]

It would be useful to generate a minimised build with all locales included and registered, similar to what Moment.js does, e.g. timeago-with-locales.min.js, so that anyone wanting to include all locales can just load that - even if it is a larger file.

#109 Attempt to add support for cancelling single timer for specific node

minified size increased to 2.02 kb :disappointed: If someone has better ideas - lets discuss them together

Also this PR fixes unpleasant issue with this code - there are a lot of "dead" timers that are stored in the array until they are explicity removed by calling cancel. By "dead" timers I mean timers that are already executed but their ids are still in the array. Potentially it causes memory leaks.

Added translations for the Georgian language.

Although not very well known, Georgian is a unique language spoken only by the citizens of Republic of Georgia (for thousands of years).

I love your library, and since I had to create a Georgian locale for my use anyway, I thought I might as well create a PR.

Not a lot of libraries have Georgian translations, so your library will stand out even more now!

Working code is on branch master.

• rewrite with es6.
• coverage test cases to 100% with jest.
• refactoring code structure.
• bundle with rollup & babel.

What to be done?

• [x] test coverage, src & locales
• [x] code of locales translated to ES6
• [x] new API design
• [x] locale file format

new API

import { format, render, cancel, register } from 'timeago.js';

// format date to string
const str = format(date, locale);

// real time render
render(dom, locale);

cancel(dom); // cancel the dom

cancel(); // cancel all

// new locale
register('new_locale', localeFunc);

Welcome to pr and discuss.

Has the implementation of a cutoff option ever been considered? This would display the original date if time distance is older than the cutoff.

This is implemented in the jQuery plugin: https://github.com/rmm5t/jquery-timeago

Would you consider a pull request for this feature?

hr.ts

const localeFunc = (number: number, index: number, totalSec: number): [string, string] => {
  // number: the timeago / timein number;
  // index: the index of array below;
  // totalSec: total seconds between date to be formatted and today's date;
  return [
    ['tek sada', 'upravo sada'],
    ['prije %s sekundi', 'za %s sekunde'],
    ['prije 1 minute', 'za 1 minutu'],
    ['prije %s minuta', 'za %s minuta'],
    ['prije 1 sata', 'za 1 sat'],
    ['prije %s sata', 'za %s sata'],
    ['prije 1 dan', 'za 1 dan'],
    ['prije %s dana', 'za %s dana'],
    ['prije 1 tjedan', 'za 1 tjedan'],
    ['prije %s tjedna', 'za %s tjedna'],
    ['prije 1 mjeseca', 'za 1 mjesec'],
    ['prije %s mjeseci', 'za %s mjeseca'],
    ['prije 1 godine', 'za 1 godinu'],
    ['prije %s godina', 'za %s godina']
  ][index];
};

rs.ts

const localeFunc = (number: number, index: number, totalSec: number): [string, string] => {
  // number: the timeago / timein number;
  // index: the index of array below;
  // totalSec: total seconds between date to be formatted and today's date;
  return [
    ['nedavno', 'ovog momenta'],
    ['pre %s sekundi', 'za %s sekunde'],
    ['pre 1 minute', 'za 1 minutu'],
    ['pre %s minuta', 'za %s minuta'],
    ['pre 1 sata', 'za 1 sat'],
    ['pre %s sata', 'za %s sata'],
    ['pre 1 dan', 'za 1 dan'],
    ['pre %s dana', 'za %s dana'],
    ['pre 1 nedelje', 'za 1 nedelju'],
    ['pre %s nedelje', 'za %s nedelju'],
    ['pre 1 mesec', 'za 1 mesec'],
    ['pre %s mesea', 'za %s meseca'],
    ['pre 1 godinu', 'za 1 godinu'],
    ['pre %s godina', 'za %s godina']
  ][index];
};

Fixes https://github.com/hustcc/timeago.js/issues/240

This is something I have found when publishing my packages to NPM, the src directory is published to NPM which the .map files refer to. There might be some alternative way to embed sourceMap src or something, but this solution has worked for me! Thanks for this package

I'm trying to render in Spanish, and am not sure how to configure timeago.

import { register, format, render, cancel } from 'timeago.js';
import {esLocal} from 'timeago.js/lib/lang/es';
register('es', esLocal);

                    const nodes = document.querySelectorAll('.timeago');
                    // use render method to render nodes in real time
                    render(nodes, 'es');

I imagine I'm not registering it correctly, but I can't find the documentation on how to do that. Thanks.