language mixup on traffic

[aymanc]

moment.locale(opts.lang || opts.language);
being called before calling the moment() function is problematic.

This will force you to use one language throughout your templates, i fixed it in a branch i'm currently using by sending the language as the 3rd parameter in the moment() function instead.

Note: The problems won't appear until you have considerable traffic and using multiple locales, the locales would get mixed up.

Best,
Ayman.

[jonschlinkert]

Please don't create issues like this. As a rule, I don't ever feel inclined to go out of my way for people who verbally abuse maintainers.

I made this library because we needed it, I'm glad others get value from it too. If you're going to use our libs, great. If you want to create issues and let us know when there is a bug, awesome. If you want to do a pr, that's fantastic. But please do not create issues to be condescending and hostile. We have a very simple policy of blocking people who are hostile and create negative energy (when we block, we block the personal across all of our libraries and orgs). Normally I would have already done this by now, but I'll assume you're having a bad day.

Moreover:

• please use backticks around code examples
• please use a title that describes the actual bug you experienced. the current title is not informative.
• If you found a bug, and you took the time to figure out the cause, and it was something this simple, it would have taken less time to just submit a pr instead of typing out the entire rant. Now I'm having to respond to the rant instead of coding. See how this negative energy destroys productivity?

This will force you to use one language throughout your templates (think about it),

Simply stating the problem is enough. I'm betting the vast majority of users just use the for dates, not i18n (think about it).

[aymanc]

Alright, it was definitely not meant to be offensive.