Skip to content

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

Closed
wants to merge 16 commits into from
Closed

Conversation

mtscout6
Copy link

@mtscout6 mtscout6 commented Aug 8, 2014

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.

@Offirmo
Copy link

Offirmo commented Aug 29, 2014

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 ?

@mtscout6
Copy link
Author

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!

@codebox
Copy link
Owner

codebox commented Mar 29, 2016

I have finally added this to npm under the name moment-precise-range-plugin so closing this pull request.

@codebox codebox closed this Mar 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants