moment().fromNow() returns 'Invalid date'

How do you run your Discord Bot?

You said: _"This worked before but it no longer works"_
Has anything changed since it worked - e.g. have you updated the environment your discord bot runs on? Has the format of 'user account created date' changed?

Are you able to modify your discord bot code to show the output of the below (specifically using hard-coded strings):

console.log('moment.format:', moment("2018-06-07T22:54:07.310Z").format());
console.log('moment.fromNow:', moment("2018-06-07T22:54:07.310Z").fromNow());

It was working before then just stopped. No code changed. No envirnoment changed with the bot. The way the dates are being parsed seem the same too.

And here's what the console outputted;

moment.format: 2018-06-07T15:54:07-07:00
moment.fromNow: Invalid date

and here's how I used it (this.client.moment is how I have moment defined):

 console.log('moment.format:', this.client.moment("2018-06-07T22:54:07.310Z").format());
console.log('moment.fromNow:', this.client.moment("2018-06-07T22:54:07.310Z").fromNow());

Not sure if I mentioned it or not, but here are the current versions I'm using:
"moment": "^2.22.2",
"moment-duration-format": "^2.2.2"
and I'm on v8.9.2 of node

I'm having similar issue with Angular 6 (ionic based app) and moment 2.22.2 returns invalid date for something as simple as this.
moment(new Date()).fromNow();
please advise.

Still happening in 2.23.0

time = moment('2017-08-08T18:29:07.000Z')
time.isValid() // true
time.toNow() // Invalid date
time.fromNow() // Invalid date

Thanks for opening this request
Hi! Thanks for filing this issue! Unfortunately, I can't reproduce this. Could you provide any other information?

It helps if you run these lines on your machines:

console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

Thanks for the reply. I am using NodeJS, so there is not a navigator environment.

new Date()).toString() Thu Jan 17 2019 06:53:11 GMT-0600 (Central Standard Time)
new Date()).toLocaleString(): 1/17/2019, 6:53:11 AM
new Date()).getTimezoneOffset(): 360
moment.version: 2.23.0
NodeJS is v11.6.0

I've been doing some testing and the conflict is an Object.prototype constructor.

Object.prototype.test = function () {
    return test
}

const moment = require('moment');

const time = moment('2017-08-08T18:29:07.000Z')
console.log(time.isValid()) // true
console.log(time.toNow()) // Invalid date
console.log(time.fromNow()) // Invalid date

I am also affected by this.
At first, I believed that using an incomplete unix timestamp (how the data is provided to me) in the constructor was the cause, but upon testing the example code in MomentJS' documentation, I found that any call to fromNow() returned Invalid Date.

Same problem here.

toString Tue Jan 07 2020 10:20:09 GMT+0100 (Central European Standard Time)
toLocaleString 1/7/2020, 10:20:09 AM
getTimezoneOffset -60
navigator.userAgent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
moment.version 2.24.0

Same here on "moment": "^2.24.0",. It works fine when run on browser but fails in nodejs. Any workaround until fixed? @marwahaha

It's a hack, but you could change the Object.prototype extensions so they're not enumerable:

console.log(moment().fromNow()); // 'a few seconds ago'
Object.prototype.randomExtension = true;
console.log(moment().fromNow()); // 'Invalid date'

Object.keys(Object.prototype).forEach(function(extension) {
  Object.defineProperty(Object.prototype, extension, { enumerable: false });
});

console.log(moment().fromNow()); // 'a few seconds ago'