-
Notifications
You must be signed in to change notification settings - Fork 89
Npm node, with i18n support #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
i18n use monent relative time concept
retrieve test
…n-concept change to have i18n with relative time from moment
…ring. Will have to live with setting thresholds globally and leaving it to get I18n support with preciseDiff
Hello @mtscout6 I tested your fork, and it displays "a few seconds" for seconds. I thought the point of this module was to be precise ?? P.S. why don't you have issues enabled on your fork ? |
First, my concern that this library addressed was primarily around accuracy in years. I have not personally dealt with nor needed seconds precision. The i18n support was enticing, hence the reason I ran with that fork. Second, I didn't realize that issues were not enabled till right now. Which I have promptly enabled. I would love pull requests to make it better! |
I have finally added this to npm under the name moment-precise-range-plugin so closing this pull request. |
This brings in PR #1 as well as changes it to work on npm. In order to get it to work on the browser you could just use browserify, or web-pack. I have published it to npm, although I would be willing to transfer or add you to the ownership; whichever you prefer.